Difference between revisions of "What to do for a release"
(new article) |
m (→Translations: wikilink) |
||
Line 10: | Line 10: | ||
make gramps.pot | make gramps.pot | ||
* commit the new <tt>gramps.pot</tt> file to svn | * commit the new <tt>gramps.pot</tt> file to svn | ||
− | * ask for all [[translators]] on [email protected] and [email protected] to update the <tt>.po</tt> files; plan to release about 1 to 2 weeks after this date | + | * ask for all [[Translating GRAMPS|translators]] on [email protected] and [email protected] to update the <tt>.po</tt> files; plan to release about 1 to 2 weeks after this date |
* ask for translators to e-mail their <tt>.po</tt> files to you; not all translators have svn access; expect to spend a bit of time checking in <tt>.po</tt> files | * ask for translators to e-mail their <tt>.po</tt> files to you; not all translators have svn access; expect to spend a bit of time checking in <tt>.po</tt> files | ||
Revision as of 08:15, 12 October 2007
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:
Contents
Translations
- announce the intent to release on the [email protected] 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 [email protected] and [email protected] 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
- login to cpanel at http://gramps-project.org/cpanel
- upload the candidate .tar.gz file into the public_html/test/ directory
- ask people to download and test from http://gramps-project.org/test/
When the candidate is ready to be released
- access the Sourceforge "admin" tab at http://sourceforge.net/projects/gramps/
- go to "File Releases"
- add a new release in the "Stable" package
- note the names of previous releases
- upload the tarball by anonymous ftp to ftp://upload.sourceforge.net/incoming/
- announce on [email protected]
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