Page History

...

1. Declare a candidate build to the community (RC) by uploading release candidate to release manager's web directory on people.apache.org. Work out any issues that are voiced.
2. Update the Readme file with the important New Function and a pointer to defect fixes for this release. Put the delivery date of the release at the top of the readme.
3. Get some to verify that all of the samples pass without issues. Integration tests and unit tests should run and known problems need to be identifed.
4. Initiate a vote on tuscany-dev mailing list for the release candidate to make the build a public release.
5. After 3 days, post the result to the devlist
6. Get approval from IPMC to make this a public release. Send a note to general@apache.org which summarizes the result of vote on devlist and include a pointer to the release in your note. 3 (+1) IPMC votes are required to make this a public release and of course no (-1).
7. Once you have IPMC support, post the release to people.apache.org.
8. update 'Download' link on the wiki and make it a goal to update or add documentation.
9. Don't forget that all this could not have been done without everyone's help. Post a congratulation note to the dev list and thank the entire team for their efforts to make this happen And thank you for the extra ordinary effort to make this happen

Good References

...

• Apache Release Management: http://incubator.apache.org/guides/releasemanagement.html
• Apache release publishing guide: http://www.apache.org/dev/release-publishing.html
• ARAT: http://code.google.com/p/arat/
• Apache Voting: http://www.apache.org/foundation/voting.html
• Signing Releases: http://www.apache.org/dev/release-signing.htmlRelease process from Apache Axis2:

Examples

http://wiki.apache.org/ws/FrontPage/Axis2C/releases/steps

• Release process from Apache Cayenne: http://cwiki.apache.org/CAY/release-guide.html
• Release process from Apache Geronimo: http://cwiki.apache.org/GMOxPMGT/release-manager-checklist.html