I started on this some time ago:
http://cwiki.apache.org/CAY/release-guide.html
We will need to add a few more items after this release cycle:
* how to check the code for compliance (there was a RAT tool used to
check our incubator release. I'll dig up the link).
* differences between SourceForge release (1.2.x) and Apache release
(2.0.x, 3.0.x)
* how to publish a release
* how to publish Maven artifacts
+1 on a rotating release admin role.
Andrus
On Jan 4, 2007, at 3:47 PM, Kevin Menard wrote:
> I propose we add some sort of checklist of tasks to complete during
> the
> due diligence process. Confluence makes these really simple and we
> could track by release. Otherwise, we could open up a bunch of JIRA
> tasks, but that seems less than ideal to me.
>
> Anyway, with a good checklist, any one of the committers ought to be
> able to do whatever is necessary to put out a new release. This might
> help take some of the burden of project management off you. Having
> said
> that, I'm not fully up to speed on all the ASF procedures, so it
> may be
> you that has to cut releases anyway.
This archive was generated by hypermail 2.0.0 : Thu Jan 04 2007 - 13:09:23 EST