Hi, The process is already somewhat documented. For example, http://cvs.apache.org/~yoavs/tomcatReleaseManager.html is my personal notes, and http://jakarta.apache.org/commons/releases/ is mostly Jakarta-general, not specific to Commons. It deviates from the process you posted in that we usually label a release alpha or beta, leave it out in the "wild" for a bit to give users a chance to use it, and then call it stable (with a new announcement).
Tomcat RMing is more complicated than others due to the relative complexity of the product itself compared to most Apache products. There are many ways to screw it up as I've found out myself with my first couple of releases. In addition specifically for this, you'd have to backport patches committed to CVS HEAD to the TOMCAT_4_1 branch, which has significantly different code in many key modules. But that's not the issue here. I'd probably be willing to do the release if we decide one is needed. The issue is how long we maintain things. We don't want to be in the business of maintaining old branches forever. There's been a stable Tomcat 5 for more than a year now, and the past few months we've been closing Tomcat 4.1 bugs with the statement that it's not actively maintained and users should upgrade. This is of course a standard practice in many organizations. I don't want to introduce life into the 4.1 branch, have users using 4.1.31, filing new bugs against it, etc. We have very limited support resources as-is and it makes no sense to stretch them to old branches. Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: Keith Wannamaker [mailto:[EMAIL PROTECTED] >Sent: Friday, August 20, 2004 10:34 AM >To: Tomcat Developers List >Subject: RE: Where's 4.1.31? > >Yoav, I haven't RM'd a release yet but if you or another RM-pro >is willing to show me what is involved I might be willing to wear >the hat for 4.1.31. Here is how I understand the process: > >- tag and create a release canidate >- email to announce@ >- wait 48 hours for show stoppers >- delcare the RC a release >- email to announce@, update jakarta site > >I'd even be willing to document this process if it is not already. > >[EMAIL PROTECTED] > > >-----Original Message----- >From: Shapira, Yoav [mailto:[EMAIL PROTECTED] >Sent: Friday, August 20, 2004 9:13 AM >To: Tomcat Developers List >Subject: RE: Where's 4.1.31? > > > >Hi, >You can't expect a 4.1.31 anytime soon. It's in a maintenance mode >where only Spec violations and security flaws are the things that would >get a new release out. We suggest the same thing we've been suggesting >for a while now, upgrade to 5.x. > >Yoav Shapira >Millennium Research Informatics > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
