What to do for a release

From Gramps
Revision as of 05:50, 13 October 2007 by Bmcage (Talk | contribs) (When the candidate is ready to be released)

Jump to: navigation, search

What to do for a release

These notes are based on a 2.2.x-based release. Specifically, these are the notes that resulted from the release of 2.2.9 in October 2007:

Translations

  • announce the intent to release on the gramps-devel@lists.sourceforge.net mailing list; ask that no further changes be committed to svn
  • build what should be the last gramps.pot file:
cd po
make gramps.pot
  • commit the new gramps.pot file to svn
  • ask for all translators on gramps-users@lists.sourceforge.net and gramps-devel@lists.sourceforge.net to update the .po files; plan to release about 1 to 2 weeks after this date
  • ask for translators to e-mail their .po files to you; not all translators have svn access; expect to spend a bit of time checking in .po files

Preparing the tarball

  • edit ChangeLog
  • edit NEWS to add a few lines
  • edit configure.in; change the following lines:
RELEASE=0.SVN$(svnversion -n .)
dnl RELEASE=1
to instead say:
dnl RELEASE=0.SVN$(svnversion -n .)
RELEASE=1
  • run the following command:
make distcheck
  • note that you should now have the gramps-2.2.x.tar.gz file

Making the candidate build available

When the candidate is ready to be released

  • update news section on this wiki
  • change reference from old to new version on the Installation page

Update the version number

  • edit configure.in; increment the version number
  • make certain the RELEASE=1 line is back to dnl RELEASE=1
  • commit to svn

See also

External links