Difference between revisions of "What to do for a release"
m (→Once the release is available: irc topic) |
m (→Making the candidate build available: correction to rc name) |
||
Line 30: | Line 30: | ||
* login to cpanel at http://gramps-project.org/cpanel | * login to cpanel at http://gramps-project.org/cpanel | ||
− | * rename the candidate from <tt>gramps-2.2.x.tar.gz</tt> to <tt>gramps-2.2.x- | + | * rename the candidate from <tt>gramps-2.2.x.tar.gz</tt> to <tt>gramps-2.2.x-0rc1.tar.gz</tt> so everyone knows this is a release candidate |
* upload the candidate <tt>.tar.gz</tt> file into the <tt>public_html/test/</tt> directory | * upload the candidate <tt>.tar.gz</tt> file into the <tt>public_html/test/</tt> directory | ||
* ask people to download and test from http://gramps-project.org/test/ | * ask people to download and test from http://gramps-project.org/test/ |
Revision as of 18:19, 17 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 final 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
- rename the candidate from gramps-2.2.x.tar.gz to gramps-2.2.x-0rc1.tar.gz so everyone knows this is a release candidate
- upload the candidate .tar.gz file into the public_html/test/ directory
- ask people to download and test from http://gramps-project.org/test/
Making the release available
- note the names of previous releases
- upload the tarball by anonymous ftp to ftp://upload.sourceforge.net/incoming/
- access the Sourceforge "admin" tab at http://sourceforge.net/projects/gramps/
- go to "File Releases"
- add a new release in the "Stable" package
- fill in name: a number such as 2.2.8 is the name for sourceforge site
- enter release notes -- usually this is the new section of the NEWS file
- add uploaded file(s) to the release by checking the appropriate check button and then clicking the "Add Files and/or Refresh View" button
- set architecture and the file type, click "Update/Refresh"
Once the release is available
- announce on [email protected], [email protected] and [email protected]
- update news section on this wiki
- update reference to the new version on the Installation page
- change the topic on the IRC channel #gramps
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