Difference between revisions of "What to do for a release"

From Gramps
Jump to: navigation, search
m (Preparing the tarball: ChangeLog now requires svn2cl)
m (Making the release available: uploads now go to frs.sourceforge.net)
Line 66: Line 66:
 
*  run the following command:  
 
*  run the following command:  
 
  make distcheck
 
  make distcheck
* upload the tarball by anonymous ftp to ftp://upload.sourceforge.net/incoming/
+
* upload the tarball using sftp to frs.sourceforge.net
 
* access the Sourceforge "admin" tab at http://sourceforge.net/projects/gramps/
 
* access the Sourceforge "admin" tab at http://sourceforge.net/projects/gramps/
 
* go to "File Releases"
 
* go to "File Releases"

Revision as of 00:15, 18 May 2008

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 final 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

svn2cl --reparagraph --include-rev --authors=src/data/authors.xml
cd po
svn2cl --reparagraph --include-rev --authors=../src/data/authors.xml
cd ..
  • edit configure.in; change the following lines:
RELEASE=0.SVN$(svnversion -n .)
dnl RELEASE=0rc1
dnl RELEASE=1
to instead say:
dnl RELEASE=0.SVN$(svnversion -n .)
RELEASE=0rc1
dnl RELEASE=1
  • run the following command:
make distcheck
  • note that you should now have the gramps-2.2.x.tar.gz file
  • note the svn commit revision number
  • create a tag in svn for the release candidate:
svn copy -r ### https://gramps.svn.sourceforge.net/svnroot/gramps/branches/gramps22 \
https://gramps.svn.sourceforge.net/svnroot/gramps/tags/gramps-2.2.x-rc1 \
-m "tag 2.2.x-rc1"
  • another example of creating a tag in svn:
svn copy -r 10392 https://gramps.svn.sourceforge.net/svnroot/gramps/branches/gramps30 \
https://gramps.svn.sourceforge.net/svnroot/gramps/tags/gramps-3.0.0 \
-m "tag 3.0.0-rc1"
  • for trunk, creating the tag is just slightly different since trunk is not within the "branch" directory; for example:
svn copy -r 9856 https://gramps.svn.sourceforge.net/svnroot/gramps/trunk \
https://gramps.svn.sourceforge.net/svnroot/gramps/tags/gramps-2.90.0-beta \
-m "tag 2.90.0-beta"

Making the candidate build available

Making the release available

  • edit configure.in; update the following lines:
dnl RELEASE=0.SVN$(svnversion -n .)
dnl RELEASE=0rc1
RELEASE=1
  • commit to svn; note the revision number
  • create a tag in svn for the release:
svn copy -r ### https://gramps.svn.sourceforge.net/svnroot/gramps/branches/gramps22 \
https://gramps.svn.sourceforge.net/svnroot/gramps/tags/gramps-2.2.x \
-m "tag 2.2.x"
  • run the following command:
make distcheck
  • upload the tarball using sftp to frs.sourceforge.net
  • 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 gramps-announce@lists.sourceforge.net, gramps-devel@lists.sourceforge.net and gramps-users@lists.sourceforge.net
  • update News section on this wiki
  • update the list of previous releases
  • update reference to the new version on the Installation page
  • change the topic on the IRC channel #gramps
  • login to cpanel at http://gramps-project.org/cpanel
  • delete the candidate builds from the public_html/test/ directory
  • update the version number at Wikipedia

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