There's no documentation that I know of. So, yes documenting the checklist is a great idea.
Also note, that we create branches of the form "0.12.x" instead of "0.12.0". This makes it easy to cherry pick commits for future bug fix releases and release candidates. Also, you might want to checkout the release.sh script (if there are some updates to it) from the master branch into 0.12.x. On Tue, Jun 4, 2013 at 7:23 PM, Benjamin Mahler <[email protected]>wrote: > Now that 0.11.0 is out, we should continue freeing up the backlog and > proceed with 0.12.0. I'll be taking care of this release and I'd like to > document the release process to make it easier for others to help out with > releases in the future. Is there already documentation somewhere? Here's > what I've inferred: > > 1. First I'll gather the JIRA tickets for the CHANGELOG. > > 2. Send out a review / commit the CHANGELOG updates. > > 3. Cherry pick the CHANGELOG onto 0.12.0. > > 4. Run 'git checkout 0.12.0 && ./support/release.sh 0.12.0 1'. > > 5. Mail [email protected] and > [email protected] a VOTE. > > 6. After a successful VOTE, add it to the website(s)? > > 7. Upload the jar to artifactory, I see Vinod is having issues with that > at the moment. > > Missing anything? >
