larryi 01/01/30 08:03:12
Modified: . RELEASE-PLAN-3.3
Log:
Final update. Modify to not promise to fix all bugs. Update Release
Criteria 9 to better specify its scope.
Revision Changes Path
1.7 +6 -4 jakarta-tomcat/RELEASE-PLAN-3.3
Index: RELEASE-PLAN-3.3
===================================================================
RCS file: /home/cvs/jakarta-tomcat/RELEASE-PLAN-3.3,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- RELEASE-PLAN-3.3 2001/01/30 14:50:14 1.6
+++ RELEASE-PLAN-3.3 2001/01/30 16:03:07 1.7
@@ -110,7 +110,7 @@
Any reported regression is a show-stopper and a release can't be made
before it is resolved.
-2. Open bugs should be resolved.
+2. Open bugs should be fixed, if possible.
3. Tomcat 3.3 should be tested with existing, complex applications ( cocoon,
bugrat, etc ).
@@ -118,7 +118,7 @@
4. Jasper must include bug fixes that were done in both 3.2.x and 4.0,
and various enhancements that are deemed appropriate.
-5. Bugs found after and during 3.2 release cycle should be fixed.
+5. Bugs found after and during 3.2 release cycle should be fixed, if possible.
6. Full review of the code, making sure the modularity and extensibility
goals have been achieved.
@@ -129,8 +129,10 @@
8. Ensure that the performance is (significantly) better than
3.2
-9. Ensure that Jasper is compatible ( as much as possible ) with the
- version used in the proposed 4.0.
+9. Ensure that Jasper is compatible (as much as possible) with the
+ version used in the proposed 4.0. This refers to behavior differences
+ outside of the JSP spec, which could create problems moving a
+ web application from Tomcat 3.3 to Tomcat 4.x.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
