> http://jakarta.apache.org/site/guidelines.html
I believe the Jakarta guidelines are the sort of thing that the board refers to as the project bylaws, like the ones posted here: * http://struts.apache.org/bylaws.html Perhaps we should just rely on the checklist to detail our release process. We could drop the references to other people's guidelines and follow our own checklist and remarks. I've added a proposed release checklist template to the website, but left it unlinked. * http://struts.apache.org/release-checklist.html -Ted. On Sat, 30 Oct 2004 00:59:28 -0500, Eddie Bush wrote: > http://jakarta.apache.org/site/decisions.html > > ^^ Link to Tomcat Procedures ^^ > > http://jakarta.apache.org/site/guidelines.html > > ^^ Overall Tomcat Guidelines ^^ > > I updated the releases documentation to point to the Tomcat > Procedures. AFAICT the remainder of the release notes look good. > Feel free to disagree. The Tomcat docs talk about a release plan. > Although they don't specifically say one is required, the docs are > written in such a way that the presumption of one is implied. > > ... not real sure where Craig's bullets would get merged to, but > someone else is welcome to do that if they have thoughts on that. > It seems redundant to that that there though - it's information > that's already there. > > Eddie > > ----- Original Message ----- > From: "Ted Husted" <[EMAIL PROTECTED]> > To: "Struts Developers List" <[EMAIL PROTECTED]> > Sent: Tuesday, October 26, 2004 2:50 AM > Subject: Re: [VOTE] HTTPD or Tomcat (once more with feeling) [was > Adopt ...] > > > On Tue, 26 Oct 2004 01:23:05 -0500, Eddie Bush wrote: >> Most of my concerns are in the Release Guidelines. It's ambiguous >> to say any release should follow the guidelines of both tomcat >> and httpd. They're decidedly different with respect to where the >> emphasis is placed. >> > > If someone can provide a link to the Tomcat Guidelines, we could > drop the link to HTTPD. > > Or, someone could merge Craig's bullets: > > ---- > > * Post what amounts to a release candidate and > announce to a limited audience (dev and user > lists) asking for testing. > > * Testing ensues ... > > * Call a vote on the release, with the options > to call it alpha, beta, stable (that's fine > with me), or withdraw (if there was some > bad problem). > > * Announce to the world and do the usual process > of distributing the bits. > > ---- > > with the "Additional remarks" on the Release Guidelines page, to > create our own version. > > -Ted. > > > -------------------------------------------------------------------- > - To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] > > > --- > avast! Antivirus: Outbound message clean. > Virus Database (VPS): 0444-3, 10/29/2004 > Tested on: 10/30/2004 12:59:29 AM > avast! - copyright (c) 2000-2004 ALWIL Software. > http://www.avast.com > > > -------------------------------------------------------------------- > - To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
