I'm +1 in general.
But we also should discuss what to do with the current trunk.
I haven't closely followed the trunk status, but there might be (significant)
changes since the 1.4.0 release?
Although the JSR-286 is supposed to be JSR-168 backwards compatible, we cannot
assume every user is going to migrate to Pluto 2.0 (immediately).
Thus we have to cater for future maintenance / bug fixes on at least the latest 1.x version too, which effectively means there will be 2 active Pluto
versions... (comparable to for instance Tomcat 5.5.x and Tomcat 6.x development).
So I think we might need to release the current trunk (as Pluto 1.1.5 or 1.2,
whatever) *before* the 1.1-JSR-286-trunk-merge branch becomes trunk.
Once the trunk is released, I suggest deleting it and then simply copying the
1.1-286-trunk-merge branch to trunk.
Note: this way we might cause some annoying svn history breakage but I see no other quick solution, short of merging the 1.1-JSR-286-trunk-merge back into trunk
which I expect will not be a trivial task.
Regards,
Ate
[EMAIL PROTECTED] wrote:
Hi all,
The JSR-286 Expert Group's work is being completed in the next few weeks.
The JSR-286 RI work lead by Torsten Dettborn should also be finished at
that time. That work started in the 1.1-286-COMPATIBILITY branch, but it
has moved to the 1.1-286-trunk-merge branch with my help. As its name
implies, the 1.1-286-trunk-merge branch now has fully integrated trunk code
into the JSR-286 code.
When the final RI work is done, Ate Duoma suggested that the code be tagged
in Subversion (remember a tag is not a release). That point would also be a
good time to move the 1.1-286-trunk-merge code into the trunk. I suggest we
change the pom version to 2.0.0-SNAPSHOT at that time.
Is this something you can support?
