Changes

Jump to: navigation, search

What to do for a release

19 bytes added, 17:50, 20 April 2012
m
no edit summary
'''What to do for a release'''
These notes are based on version 3.3.0, released in June 2011{{version}}. The steps assume a working <tt>gramps{{stable_branch}}</tt> source directory. See [[Running a development version of Gramps]] if this is not the case.
==Translation update==
Using the <tt>Changelog</tt> files generated with <tt>svn2cl</tt> in the step above, edit and update the <tt>NEWS</tt> file.
Commit the NEWS file. Note the svn commit revision number, which you'll need in the next step when you create the subversion tag:
svn commit -m "update for 3.3.0 {{version}} release"
Committed revision 17751.
==Subversion tag==
Using the previous commit revision number, create a tag for the new release:
svn copy -r 17751 https://gramps.svn.sourceforge.net/svnroot/gramps/branches/maintenance/gramps{{stable_branch}} https://gramps.svn.sourceforge.net/svnroot/gramps/tags/gramps-3.3.0 {{version}} -m "tag 3.3.0{{version}}"
Committed revision 17752.
Check out the new tag:
cd ..
svn co https://gramps.svn.sourceforge.net/svnroot/gramps/tags/gramps-3.3.0{{version}} cd gramps-3.3.0{{version}}
Modify <tt>configure.in</tt> to indicate an official release:
make distcheck
Note you should now have the file <tt>gramps-3.3.0{{version}}.tar.gz</tt>, approximately 8 MB in size.
==Making the source tarball available==

Navigation menu