This how to is under development but it might help. Feel free to contribute.

• Are the translations up to date, are the translator aware of you going to release.
• All patches are applied and all known critical bugs fixed.
• Do you have the feeling: “Yes, this code ready to be released upon the world, everyone should be able to enjoy it” ;)

1. Release information: ChangeLog, NEWS.
2. Common information: README, AUTHORS, THANKS, TODO (when present).

1. Update version in the configure script template configure.in.in or configure.ac.in.
2. Remove git from <package>_version_tag.
3. Check the build dependencies.

1. Run ./autogen.sh.
2. Run make distcheck
3. Check auto generated files: INSTALL, COPYING
4. If at this stage everything works, commit all changes for release to master.
5. Now you are ready to tag the current master:
   

   git tag -a <package version/tag name>
   git push
   git push --tags

You can sign tags with a GPG key by adding an additional -s or -u <key id> parameter to git tag -a <package version/tag name>. For more information about tagging read the ''git-tag'' manual.

1. Edit configure.in.in or configure.ac.in.
2. Change package_version_major, package_version_minor and package_version_micro version to the next version.
3. Re-add svn to package_version_tag.