Page History

...

• Analyze Open Issues
• Issue Fixing - ongoing - all issues should be resolved or moved
• Developers create signatures - who should be included in this list?
• Licence Audit and Legal Audit - including headers, dependencies, LICENCE and NOTICE files
• Documentation – Check installation and build documentation for accuracy, create status document, create release notes
• Create Release branch on SVN – sign binaries, permissions 22nd Oct
• Test, test, test!
• Vote on release
• Request approval from Incubator PCM
• Upload to incubator dist
• Check permissions
• When mirroring has taken place update website and announce the release.

Open Issues

A list of outstanding issues is generated from Jira. This list is posted to the project developer list with suggestions to either implement for the release or postpone for the next release. After community discussion JIRA is updated accordingly.

When deciding whether to implement an issue for this release be aware of taking on too much. It is more important to get a release out than to complete all features. Release early, release often.

Once complete this process gives a clear definition of what will be included in the release and allows timescales to be estimatedThe mailing list was used to vote on whether open issues could be moved to the next version or had to be fixed for this.

Issue Fixing

Each issue for the release to be fixed then the fixes to be tested, reviewed and accepted.

...