12:13 p.m.
We currently have a vfs version of 2.0.0.Beta18 in jbossas, but the
http://jira.jboss.com/jira/browse/JBVFS project only has releases
defined up to 2.0.0.Beta12. All changes in 2.0.0.Beta13-18 are in the
2.0.0.CR1 or no version. We need to have a jira release for every maven
release we do.
12:22 p.m.
New subject: Can't perform a vfs release without updating the JBVFS releases
Also, I don't see svn commits for closed vfs issues like the following:
http://jira.jboss.com/jira/browse/JBVFS-35?page=com.atlassian.jira.plugin...
You need to be including the jira issue in the svn commits that apply to
the issue. JBVFS-35 is marked as resolved for 2.0.0.CR1, but it must be
in some previously release. I can guess its 2.0.0.Beta18 based on the
date, but I don't know.
Scott Stark wrote:
We currently have a vfs version of 2.0.0.Beta18 in jbossas, but the
http://jira.jboss.com/jira/browse/JBVFS project only has releases
defined up to 2.0.0.Beta12. All changes in 2.0.0.Beta13-18 are in the
2.0.0.CR1 or no version. We need to have a jira release for every
maven release we do.
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
12:59 p.m.
New subject: Can't perform a vfs release without updating the JBVFS releases
Yeah, I got caught on release frenzy, neglecting JIRA. :(
I'll create matching release reports asap.
Sent from my iPhone
On Jun 21, 2008, at 19:22, Scott Stark <sstark(a)redhat.com> wrote:
Also, I don't see svn commits for closed vfs issues like the
following:
http://jira.jboss.com/jira/browse/JBVFS-35?page=com.atlassian.jira.plugin...
You need to be including the jira issue in the svn commits that
apply to the issue. JBVFS-35 is marked as resolved for 2.0.0.CR1,
but it must be in some previously release. I can guess its
2.0.0.Beta18 based on the date, but I don't know.
Scott Stark wrote:
> We currently have a vfs version of 2.0.0.Beta18 in jbossas, but the
http://jira.jboss.com/jira/browse/JBVFS
> project only has releases defined up to 2.0.0.Beta12. All changes
> in 2.0.0.Beta13-18 are in the 2.0.0.CR1 or no version. We need to
> have a jira release for every maven release we do.
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
1:07 p.m.
New subject: Can't perform a vfs release without updating the JBVFS releases
It's really a small overhead that pays off later on when you're trying to find out
what when
into which release. Some basic housekeeping is necessary, not just for VFS but for all
projects.
Ales Justin wrote:
Yeah, I got caught on release frenzy, neglecting JIRA. :(
I'll create matching release reports asap.
Sent from my iPhone
On Jun 21, 2008, at 19:22, Scott Stark <sstark(a)redhat.com> wrote:
> Also, I don't see svn commits for closed vfs issues like the following:
>
http://jira.jboss.com/jira/browse/JBVFS-35?page=com.atlassian.jira.plugin...
>
>
> You need to be including the jira issue in the svn commits that apply
> to the issue. JBVFS-35 is marked as resolved for 2.0.0.CR1, but it
> must be in some previously release. I can guess its 2.0.0.Beta18 based
> on the date, but I don't know.
>
> Scott Stark wrote:
>> We currently have a vfs version of 2.0.0.Beta18 in jbossas, but the
>> http://jira.jboss.com/jira/browse/JBVFS project only has releases
>> defined up to 2.0.0.Beta12. All changes in 2.0.0.Beta13-18 are in the
>> 2.0.0.CR1 or no version. We need to have a jira release for every
>> maven release we do.
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
6:04 p.m.
New subject: Can't perform a vfs release without updating the JBVFS releases
Use JIRA. I am sure neither our brains nor any notepads can hold all
the changes we make on a regular basis. :)
Ales Justin wrote:
Yeah, I got caught on release frenzy, neglecting JIRA. :(
I'll create matching release reports asap.
Sent from my iPhone
On Jun 21, 2008, at 19:22, Scott Stark <sstark(a)redhat.com> wrote:
> Also, I don't see svn commits for closed vfs issues like the following:
>
http://jira.jboss.com/jira/browse/JBVFS-35?page=com.atlassian.jira.plugin...
>
>
> You need to be including the jira issue in the svn commits that apply
> to the issue. JBVFS-35 is marked as resolved for 2.0.0.CR1, but it
> must be in some previously release. I can guess its 2.0.0.Beta18 based
> on the date, but I don't know.
>
> Scott Stark wrote:
>> We currently have a vfs version of 2.0.0.Beta18 in jbossas, but the
>> http://jira.jboss.com/jira/browse/JBVFS project only has releases
>> defined up to 2.0.0.Beta12. All changes in 2.0.0.Beta13-18 are in the
>> 2.0.0.CR1 or no version. We need to have a jira release for every
>> maven release we do.
6027
days inactive
6027
days old
jboss-development@lists.jboss.org
4 comments
4 participants
participants (4)
-
Ales Justin -
Anil Saldhana -
Dimitris Andreadis -
Scott Stark