Stefano Bagnara wrote:

I would like something more specific about 2.3 and generic about 2.4.
I would be +1 to the following roadmap:

1) 2.3 is release candidate: we don't change anything if not to fix major/medium bugs

+1 Noel and you are right, I would really like to have jspf sooner :'( but I think it's more important to finalize 2.3.0 asap.


2) 2.4 is the next 2.x release (we had this in roadmap until you decided at apachecon to keep only 3.0 ;-) ) and is storage compatible with 2.2 (like 2.3). We can backport here *anything* from trunk if we keep storage compatibility and mailet api compatibility.

+1


3) 3.0 will be the next major release including any backward incompatibility issue.

+1


Currently IIRC anything we have in trunk could be part of the 2.4 release as we didn't introduce any incompatibility.

If we want to follow this roadmap I would avoid to commit anything 3.0 specific in trunk until we have a 2.3.0 final out. Then I would start a 2.4.0 branch from the trunk of that moment and from that point we would still have 2 active tree (2.4 branch and trunk for 3.0).

The main difference from your proposal is that I would put in every non-incompatible change in and I would try to create it from trunk instead of starting a selective merging work.

+1 if we are also able to keep config.xml unchanged (confining differences only to james-smtphandlerchain.xml).


Otherwise I will not be +1 because I think that we would start having too much things to vote upon about 2.4 mergin, we would start having 3 active trees (2.3, 2.4 and trunk) and too many critical issues.

About your specific proposal (having a 2.4 as a 2.3+fast fail+launcher) I'm currently -1 because I think fast fail need much more work and the launcher is to be tested and there is much more that deserve inclusion in a 2.4 release before (almost all we currently have in trunk).

Furthermore the launcher stuff needs to be discussed because we may need to change our binary releases: the commons-daemon has 4 different binaries and different solutions for 4 platform (freebsd, macosx, win, linux). Tomcat does OS specific releases, we currently have a single release... we should test and include at least linux and windows and this would take much more.

Stefano



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to