1.3.1 backport strategy

[Matt Bishop <mb...@infowave.com>]

I'd like to propose that the v1 backport to JDK 1.3.1 follows this strategy:

1. Code changes should eventually go into the v1 trunk rather than in a
separate line.  This will avoid having to maintain two versions of the same
product.  The committer may want to branch initially, but the end result
should be that v1 is 1.3.1-compliant out of the box.

As an example of the opposite approach, Tomcat 4.1 ran a JDK 1.4-only
version for a while, but it proved to be too much of a pain to preserve it.
They now ship one version only.

2. All existing functionality needs to be preserved, for instance, nested
exceptions.

3. Jars are introduced only when absolutely necessary.  An example to follow
is Xerces, which now includes resolver.jar from XML-Commons.

4. Code changes are submitted in small pieces to maintain stability and
feature-correctness.  This means that the project will still be built with
JDK 1.4 until all the changes have been applied.  The last change will be to
switch build.xml over to using 1.3 instead of 1.4.



- ---------------------------------------------------------------------
To unsubscribe, e-mail:   xmlbeans-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/