Release proccess (draft proposal)

Apache Geode has the following steps for each release: 

Preparing

- Create a release branch from develop

- Build and run tests++

- Sign it using GPG key

GPG key for signing artifacts ?

Publishing

Check details about how to publish to Nexus or repository.apache.org:

http://www.apache.org/dev/publishing-maven-artifacts.html#common

Execute the following steps: …

Call for a vote (PMCs)

A majority vote will be called in the mailing list and will wait for 72 hours (3 days) and if it passes (http://hadoop.apache.org/bylaws#Decision+Making) the release will then be published.

The release may initially be a candidate (RC) that after formally being reviewed and approved by another majority vote will become a public GA release.

Update the website and documentation

In order to complete the release it is mandatory to review and update the website content as well as provide documentation about the new features or changes made for the release.

These are the steps you need to follow:

- Clone website repository

 - Update pages and run gradle website task which will generate content under …

- Clone documentation repository run gradle generateDocs 

 - Update documentation and run 

Publish announcement

After release is complete post a message on the dev list, blog, tweet, sing about it.  Make it public.  

FAQ

 http://www.apache.org/dev/release.html