>  A few weeks ago, Elliot volunteered to do a Pluto 1.1.5 release and was
> preparing that in the 1.1.x branch, which, I believe, is a clone of the
> trunk.

Perhaps we should review the JIRA issues slated for 1.2.0, make sure that
the fixes have been applied to the 1.1.x branch where applicable, and then
reassign the issues to other branches as appropriate.  I looked at a few
of the issues very briefly and it looks like some of then have been
applied to trunk but not to the other branches.  I do think that Pluto 2.0
should become the trunk and the 1.1.x branch should be for JSR 168/Java
1.4 compatibility.  I think that a 1.2.0 release would not add anything to
Pluto except for an unnecessary dependency on Java 5.

-- Ben

Reply via email to