Norman Maurer wrote:
> Noel J. Bergman schrieb:
> > Now, let's consider next-major. As far as I know, we agree that
> > the code in trunk will branch to be next-major. BUT, we also
> > agree that there is code in trunk that may not survive the pruning.
> > For example, perhaps none of the IMAP stuff survives to ship in
> > next-major. We decide that in order to have a release in some
> > timeframe, everything else is stable enough, but not certain other
> > parts. Those issues would be resolved in trunk, but *not* resolved
> > in next-major. Do you understand now why I am making this point
> Well i now better understand your point.. But i not agree with you.
> if we remove some fixes from next-major or realize that its not
> fixed we should just remember changing JIRA.
"Remembering" is always a big problem. The tool is supposed to do the
remembering for us. :-)
See also my comments to Vincenzo for more elaboration on why trunk !=
next-major for release planning and labeling purposes.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
