In order to ensure that Galago releases generally turn out properly, a number of things must be done before a release.

Prior To Release

  1. Two weeks prior to a release, if translatable strings have been at all changed, an e-mail to galago-i18n should go out, informing translators that they need to update and submit new .po files.

During Release

  1. All configure.ac files must have their versions bumped.
  2. Dependency versions in configure.ac files must be updated to reflect the new upcoming released versions.
  3. The NEWS files must be updated for the new version, along with any information and a release date.
  4. make distcheck must be performed.
  5. Sourcecode tarballs must be uploaded to http://www.galago-project.org/files/releases/source/.
  6. The releases file on the web server must be updated.

Post Release

  1. galago-announce must be e-mailed.
  2. Freshmeat.net should be updated.