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.
-- Kevin> -----Original Message----- > From: Andrus Adamchik [mailto:andru..bjectstyle.org] > Sent: Thursday, January 04, 2007 8:37 AM > To: cayenne-de..ncubator.apache.org > Subject: Re: [VOTE] Re: Cayenne 2.0.2 (and 1.2.2) > > Another note (something I overlooked, getting too excited > about the first release from Apache and all that). We'll > still have to do all the due diligence once the release > artifacts are posted, ensuring that (a) they work and (b) > there are no legal issues, like missing license headers and all that. > > So we will have another (consequential) vote once a release > admin (I guess that's me at the moment) posts the release files. > > Andrus
This archive was generated by hypermail 2.0.0 : Thu Jan 04 2007 - 08:48:49 EST