Noel J. Bergman wrote:
Stefano and I certainly had a misunderstanding over his intent for "2.4" (the next minor release), due to the subject heading. If were were in physical proximity, I'd shake his hand. We've already apologized for the misunderstanding, and had a very long chat (each of us missed a meeting or two to have it).
As I wrote to Noel in IM I think most of the misunderstanding is because we have this numbers in our minds: RELEASE NOEL STEFANO next-minor 2.4 n/a (2.4) next-major n/a (3.0) 2.4 (2.5 if next-minor) next-grater 3.0 3.0 I always understood this difference in version numbers we have in our minds, and that's why I started using "next-labels" to try to slow down the flame about numbers. But everytime a number is used again the flame starts again. As I said multiple time I believe we can decide the number when we'll be ready to branch but we should avoid number flames until that day. In IM I explained Noel that next-major is different from what it described as 3.0 because I described it as a backward-compatible (storage+config) release (like his 2.4/next-minor). The only difference between next-minor and next-major is that next-minor would include a small set of features selected by trunk and should be released sooner (Dec2006), while next-major would include all the features we have in trunk and would have a longer release cycle (Mar2007). If we also add that the "3.0"/v3 number has also been used years ago to define even something else (in wiki we have mailet-v3 and james-v3 pages describing things that won't probably be part of next-minor/next-major release and some other things that maybe we already included in 2.3) it is much more clear why numbers are creating the hell here. I know that next-* is not a solution to our problems, but I don't have a better solution to this: if anyone has a better way I can only be happy for this. That said once the roadmap vote will be closed I'll try to make a "wiki page/status file/ml message/jira version" to describe what we have in trunk, what I think must be included in next-major, what I think could be included, what I think cannot be included. And I hope we can find an agreement on next-major without too much discussion. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
