larryi 01/09/17 19:44:45
Modified:.RELEASE-PLAN-3.3
Log:
Update to current status.
Moved Bug 1798 to RC2 just to provide a little more time to verify that we
can't duplicate it.
Revision ChangesPath
1.14 +24 -19jakarta-tomcat/RELEASE-PLAN-3.3
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 13, 2001 12:57 PM
Subject: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3
> larryi 01/09/13 12:57:38
>
> Modified:.RELEASE-PLAN-3.3
> Log:
> Update
larryi 01/09/13 12:57:38
Modified:.RELEASE-PLAN-3.3
Log:
Update to the release plan. Also:
Bugs 3572 and 3577 have been added as required for RC1
Bug 3581 has been added as required for RC2
Bug 1482 has been moved to the "fixed in 3.3" catagory
Revision
larryi 01/06/20 21:42:10
Modified:.RELEASE-PLAN-3.3
Log:
Update release plan to add Milestone 4 and adjust dates
Revision ChangesPath
1.12 +21 -3 jakarta-tomcat/RELEASE-PLAN-3.3
Index: RELEASE-PLAN-3.3
age-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, May 15, 2001 3:00 PM
>To: [EMAIL PROTECTED]
>Subject: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3
>
>
>larryi 01/05/15 05:59:53
>
> Modified:.RELEASE-PLAN-3.3
> Log:
> Upd
larryi 01/05/15 05:59:53
Modified:.RELEASE-PLAN-3.3
Log:
Update to move getRequestURI problem to Beta 1.
Indicate requirement in Milestone 3 to check security problem of URL's with
escape sequences being able to reveal JSP source.
Indicate requirement in Beta 1
80E6
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>Sent: Friday, May 11, 2001 10:23 PM
>To: [EMAIL PROTECTED]
>Subject: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3
>
>
>larryi 01/05/11 13:22:59
>
> Modified:.RELEASE-PLAN
larryi 01/05/11 13:22:59
Modified:.RELEASE-PLAN-3.3
Log:
Update release plan. Issues and priorities aren't final and will be updated
as needed.
Revision ChangesPath
1.9 +68 -10jakarta-tomcat/RELEASE-PLAN-3.3
Index: RELEASE-PLAN-3.3
==
larryi 01/01/30 17:55:38
Modified:.RELEASE-PLAN-3.3
Log:
Update per Jon's suggestion. I specified "resolved", as supported by
Bugzilla, to indicate that some bugs may not be fixed. But, as Jon requested,
we need to make sure all bugs are addressed. None should slip t
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 ChangesPath
1.7 +6 -4 jakarta-tomcat/RELEASE-PLAN-3.3
Index: RELEASE
larryi 01/01/30 06:50:18
Modified:.RELEASE-PLAN-3.3
Log:
Move Milestone 1 back a week and fix Milestone 2 to be about midway
between Milestone 1 and Beta 1.
Fix some indentation.
Revision ChangesPath
1.6 +5 -5 jakarta-tomcat/RELEASE-PLAN-3.3
larryi 01/01/23 12:45:20
Modified:.RELEASE-PLAN-3.3 STATUS.html
Log:
Another round of changes, including a spellcheck pass.
I may be done, assuming I haven't missed something important.
Revision ChangesPath
1.5 +17 -16jakarta-tomcat/RELEASE-PLAN-3
larryi 01/01/22 13:21:45
Modified:.RELEASE-PLAN-3.3 STATUS.html
Log:
Some updates the schedule and move open items to STATUS.html.
Filled in my name as Release Manager.
Added action items to the Release Preparation section of STATUS.html.
I'll make another pass
costin 01/01/20 11:28:21
Modified:.RELEASE-PLAN-3.3
Log:
Added a paragraph about the release team and release manager, listing
the current volunteers. ( the final list will be of course decided
in the voting process ).
Added an action item to add a credits page wit
I also think it would be good idea to require Jasper's JspServlet still
function properly if used in Tomcat 3.3, even though Tomcat 3.3 now uses
an interceptor to manage JSP compilation. (Jasper is still used for
translation to servlet source, but the interceptor controls the
rest).
+1
(We u
costin 01/01/18 19:28:00
Modified:.RELEASE-PLAN-3.3
Log:
- incorporate Jon's suggestions: specify that the release team will
coordinate the support, the milestones will be periodical,based on
the RM decision, +1 commiters will decide what goes in during beta,
added me
Larry Isaacs wrote:
> A couple of comments:
>
> I would like to see a goal added like the following:
>
> X. With respect to JSP 1.1 issues, insure that Jasper in Tomcat 3.3
> remains compatible with Jasper in Tomcat 4.x.
>
Larry, are you thinking of "compatibility" from the functional viewpoint
A couple of comments:
I would like to see a goal added like the following:
X. With respect to JSP 1.1 issues, insure that Jasper in Tomcat 3.3
remains compatible with Jasper in Tomcat 4.x.
and under Release criteria something like:
X. Port all appropriate JSP 1.1 related changes from Tomcat 4.
to finally resolve
this issue through the proper process.
Matt Pangaro
Loki Technologies
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 18, 2001 2:38 AM
Subject: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3
> costin 01/0
on 1/17/01 11:38 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> costin 01/01/17 23:38:24
>
> Added: .RELEASE-PLAN-3.3
You are missing the word "support" in this entire document. It has already
been stated that it is a *requirement* in the PMC meeting that in order for
a
costin 01/01/17 23:38:24
Added: .RELEASE-PLAN-3.3
Log:
Initial checkin for the release proposal.
Revision ChangesPath
1.1 jakarta-tomcat/RELEASE-PLAN-3.3
Index: RELEASE-PLAN-3.3
==
21 matches
Mail list logo
