Changes

Jump to: navigation, search

What to do for a release

79 bytes removed, 07:05, 19 May 2012
m
Reverted edits by Romjerome (talk) to last revision by PaulFranklin2
'''What to do for a release'''
These notes are based on version {{version}}3.3.0, released in June 2011. The steps assume a working <tt>gramps{{stable_branch}}gramps33</tt> source directory. See [[Running a development version of Gramps]] if this is not the case.
==Translation update==
Run the following steps:
cd gramps{{stable_branch}}gramps33
svn update
cd po
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 {{version}} 3.3.0 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}} gramps33 https://gramps.svn.sourceforge.net/svnroot/gramps/tags/gramps-{{version}} 3.3.0 -m "tag {{version}}3.3.0"
Committed revision 17752.
Check out the new tag:
cd ..
svn co https://gramps.svn.sourceforge.net/svnroot/gramps/tags/gramps-{{version}}3.3.0 cd gramps-{{version}}3.3.0
Modify <tt>configure.in</tt> to indicate an official release:
make distcheck
Note you should now have the file <tt>gramps-{{version}}3.3.0.tar.gz</tt>, approximately 8 MB in size.
==Making the source tarball available==
==Post-release==
* in <tt>gramps{{stable_branch}}gramps33</tt>, bump the version number in <tt>configure.in</tt> and <tt>src/const.py.in</tt>
* in <tt>trunk</tt>, merge forward the <tt>NEWS</tt> file

Navigation menu