james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman" <n...@devtech.com>
Subject RE: Next-Major and trunk: AGAIN (Was: [jira] Updated: (JAMES-663))
Date Wed, 22 Nov 2006 16:04:40 GMT
Vincenzo Gianferrari Pini wrote:

> So what you mean is that the right thing to do is, if someone plans to
> have something fixed/working for next-major is to *add* the next-major
> fix version *without removing* the trunk label, right? Sounds correct.

YES!  :-)  It appears that I was far too brief in my original e-mail.
Stefano had removed trunk as a version and changed it to next major.  I
finally asked him to please stop doing that, but apparently the request
wasn't clear enough.

A problem with labeling by intent is that we may end up removing the code
from next-major, which means that someone would need to go back and remove
next-major as the label.  Right now, there are quite a few items listed
against Next Major that might not survive the release cycle, especially if
we want that to be shorter rather than longer.  It would be best to have
trunk *AND* next-major if it really looks likey to surivive, rather than
force everything to be against next-major as a label for trunk.

	--- Noel

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message