Release Management

This Page is meant for the Release Manager to use as a guide for releasing a new version of FIFE.

Procedures

Pre-Release

Phase 1

1. Hold a planning meeting for the release
   • Decide on a realistic release date with the team
   • Plan out any release specific tasks that have to be done
   • Ensure everyone agrees that the open tickets can in fact be resolved a week or two BEFORE the release date
2. Make the release date public (post on the blog)
3. Update the Release Schedule article with your release plan
4. Create any release specific tickets in trac. Also ensure there is a milestone for the proposed FIFE version

Phase 2

1. Review the Release Schedule and ensure you will reach the release date.
2. Announce any changes to release date on the blog
3. Update pertinent documentation

Phase 3

This phase begins after there are no more planned updates to trunk. I.e. most work has been completed

1. Ensure that the <FIFE>/README, <FIFE>/CHANGES and <FIFE>/INSTALL files are all up to date
   • Add release notes to REAMDE
   • Add any changes to CHANGES
   • Known issues go into README also
2. Update the source documentation
   • Change directory to the root of FIFE and run python ./tests/analyzers/dep_analyzer.py
   • Generate the dependency graphs (generated in previous step and located in <FIFE>/docs/dependencies) in PNG and PostScript format using graphviz
3. Make another announcement about the release
   • Emphasize the release date
   • Touch on the new features

Release Day

1. Package files and upload to Sourceforge. See: Release_packaging
2. Make official announcement
   • Update the FIFE blog
   • Update the SourceForge blog
3. Close the Milestone in Trac
4. Update the Release Schedule and mark all tasks as completed
5. Update the wiki front page link to the RELEASE NOTES under the Help heading.