My $0.02 inline below...
In my opinion if we call head 2.0 and start adding JEE 5 features
to it, there will never be any more j2ee 1.4 releases with added
functionality. We will have a couple bug fix 1.0 releases, then a
year or so while we try to finish JEE 5. I don't think this is
acceptable.
I strongly recommend against using 2.0 the trunk if 2.0 is to include
the JEE 5 features. The trunk should always remain as stable
development, as close to the latest supported release as possible.
Unstable features, features that take a long time, or prototypes
should always be implemented on a development/feature branch, never
on the trunk.
his point, I think we should label head 1.1-SNAPSHOT and work on
any features that require 1.5 in one or more branches, labelled by
feature.
I agree completely... but would like to mention that the entire tree
does not need to be branched, you could have a branch for a single
module, or a sub-set of modules. However, this will be much easier
once we've moved to Maven 2.
* * *
I think at this point, the trunk should be used for feature
development for 1.1, perhaps even for staging for a switch to Maven
2... though ideally Maven 2 should be done on a dev branch, but
Subversion is still not the best at automatically merging, so it may
be easier to use the trunk.
Um... and I don't think there is any way to avoid managing several
active dev & release branches. Just keep the required branches
modules to a minimum and it should be manageable.
Anyways, just my opinion... not sure that matters :-P
--jason
