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 15:49:08 GMT
Danny Angus wrote:

> J├╝rgen Hoffmann wrote:
> > And if trunk == next-major, where is the difference?
> > Why is everyone so touchy about the term?

> The issue is that it has no meaning.

Well, it's a label.  Frankly, I'm almost getting used to it.  I agree that
it has no meaning in the long-term, since it is a floater, and eventually
needs to have a real label attached to it, but that's a minor point.

> We all have our own ideas about what the next major release is, but
> the term "next_major" is not defined.

Well, that is another problem, which I mentioned earlier today.  Stefano and
Norman appear to feel that there was a vote to cast in stone what goes into
next-major.  I appear to have been cast as the official naysayer (ironic,
but addressed in another e-mail), but it appears that no one who voted for
the plan actually agreed with it at the level assumed by Stefano and Norman.
So that's an unresolved tension.

> we need to AGREE on the labels and their meanings.

Again, I just asked that he stop removing trunk from the list of versions in
JIRA, since trunk *IS* the actual place holding that code, and (to be
specific) when we branch next-major, it may or may not have (almost
certainly will not have) all of the issues closed that are closed in trunk.

Clearly my request has escalated beyond all proportion for what was
intended.

	--- Noel



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


Mime
View raw message