confusa

Getting started

So, you are going to manage a Confusa-release, are you? Great!

Now, before we get started. A few things must be in place before you can release a version.
- Create a milestone for the version. Currently, we only use milestones for versions, but you are of course to tie major events to a dedicated milestone. Just be sure to add a milestone for the version and tie the associated milestones to the version-stone.
- Set a release-date.
- Make a plan of all major components that shall go into the version.

Prior to release (version checklist)

- Are there any pending email-discussions that should be taken into consideration?
- Are there any open tickets that could affect the stability and robustness of the release?
- Is the milestone-text for the release accurate (does it reflect the actual version being released)?
- Has the test-matrix for the version been properly filled out?

Ready to release

- Update all the translations, pull from the Feide RnD translation portal to get the dictionaries up to date.
- Bump the version, add a name for the release. Add to list of releases
- Tag and sign the version, push to the repository
- Create the package and distribute the shiny, new version of Confusa to the world
- Write the announce-mail and send to “appropriate people” (whoever has expressed interest in the development will most likely be interested in new releases. Don’t worry, they’ll tell you if you’re bothering them (-; ).