Page History

...

1. Keep Jiras under control during the milestone. Make sure new opened ones are targeted for the appropriate release, and the backlog is decreasing.
2. Make sure the new function Jira are marked appropriately (since they will be used in the ReadMe file creation).
3. Look for Jira's that have patches attached to them and get the code integrated early in the cycle. Don't wait until the last minute.
4. Make sure that you begin to obtain clean versions for all SNAPSHOTs in the build. This can sometimes be a lengthy process as dependent packages are sometimes not available.
5. Lay out a plan for the distributed execution of the test suites (unit tests, integration tests, scenarios)
6. Ensure that all of the licenses are valid and replacements/remediation should be done.
7. Make sure that you remind the community that all modules should have the appropriate header file with the appropriate copyright statement.
8. Prepare for signing/authenticating distro files
   1. identify/install s/w for public key infrastructure stuff and MD5 message digest generation
   2. Create a PGP key for signing files
   3. Lodge your PGP key with a keyserver
   4. Put your public key in the svn KEYS file
9. Get set up for easy file transfer to people.apache.org
   1. Identify/Install clients for ssh, secure copying and secure ftping
   2. Establish authentication with people.apache.org by key
10. Ensure that there is inter-module understanding of how we plan to sequence releasing modules and requesting IPMC votes
11. ensure that our apache mentors know Tuscany's plans with respect to releases

Exiting the release cycle

...