Looking at someone else's release process might also provide insights. Whirr is a pretty good one imo. https://cwiki.apache.org/WHIRR/how-to-release.html
Patrick On Mon, Aug 1, 2011 at 4:10 PM, Andrei Savu <[email protected]> wrote: > We should probably follow the best practices listed in the following guide: > > http://incubator.apache.org/guides/releasemanagement.html > > From my experience we will need to go through a few RCs in order to > fix all the licensing issues. > > -- Andrei > > On Mon, Aug 1, 2011 at 3:25 PM, Andrew Bayer <[email protected]> wrote: >> (I wanted to get this on the wiki but I don't yet have wiki write access, so >> here's an email!) >> >> What exactly do we need to do in order to push out a first release, based on >> the current code? Here's what I know of, but I'm fairly sure there's more >> that I'm not as clear on: >> >> - Get the license headers in place for every pertinent file - >> https://issues.apache.org/jira/browse/BIGTOP-2 is for this, and assigned to >> me. I'll get this dealt with in the next couple days. >> - Define exactly what it is we're releasing for the first release - what >> platforms do we support? >> - Some general code cleanup - e.g., >> https://issues.apache.org/jira/browse/BIGTOP-3 for removing .gitignore >> files. >> - ...I honestly don't know what else we need to do. =) >> >> This is my first Apache project/release, so I don't know what other checkbox >> issues need to be dealt with besides the license headers. >> Suggestions/pointers/etc would be helpful. >> >> Once I've got wiki write access, I'll put this up on the wiki and let >> everyone know where it is, so that we can update it communally. >> >> A. >> >
