Perhaps we should just use the release checklist as our guidelines. We could put a copy under SVN and then say
"The release process is described by a checklist <link>, which the Release Manager may post to the wiki <link> and use as the basis of the Release Plan." Which is what we've been doing anyway :) -Ted. On Tue, 26 Oct 2004 12:11:06 +0100, Niall Pemberton wrote: > My 2 cents.... > > * Release plans are a good idea IMO and I'd prefer them being a * > must* rather than *may* - since it takes a while to get a release > out, its a good way of communicating where its at. > > * I think test builds such as 1.2.5 should be on the aquiring page, > hopefully that will encourage a wider audience to try them out - > maybe the first heading on the page should be changed from > "Aquiring Struts" to "Released Builds" and then it would be clearer > what the status is. > > * +1 for Tomcat style release. > > > Niall --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
