Changes

'''What to do for a release'''= Guidelines for version 4.0 =

These notes are based on version 34.40.10alpha1, released in August December 2012. The steps assume a working <tt>gramps34gramps40</tt> source directory.  ==Translation update==Run the following steps: cd gramps40 svn update cd po See python update_po.py -p # or intltool-update -p , .genpot.sh see [[Running Translation_environment4|New environment]] svn diff gramps.potIf there have been changes, you'll need to commit <tt>gramps.pot</tt> and ask translators to update their <tt>.po</tt> files before you can make a development release. ==Release name==Refer to (and update) the [[Previous releases|list of previous releases]] to select an appropriate name. ==Changelog and NEWS file==Create the changelog files: svn2cl --reparagraph --include-rev --authors=data/authors.xml cd po svn2cl --reparagraph --include-rev --authors=../data/authors.xml cd .. 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 4.0.0-alpha1 release" Committed revision 20810. ==Working on VERSION== Modify <tt>setup.py</tt> to indicate an official release: gedit setup.py and update the version of for the release: VERSION = "4.0.0-alpha1"Save change.  svn commit -m "make official release" setup.py The version number should be the same on "about" dialog: python Gramps.py ==Subversion tag==Using the previous commit revision number, create a tag for the new release: svn copy -r 20810 https://svn.code.sf.net/p/gramps/code/branches/maintenance/gramps40 https://svn.code.sf.net/p/gramps/code/tags/gramps-4.0.0-alpha1 -m "tag 4.0.0 alpha1" Committed revision 20811. ==Changelog and source tarball==The Changelog files are required for the source tarball, but do not commit to subversion: svn2cl --reparagraph --include-rev --authors=data/authors.xml cd po svn2cl --reparagraph --include-rev --authors=../data/authors.xml cd ..Create the official source tarball: python setup.py sdist Note you should now have the file <tt>dist/gramps-4.0.0-alpha1.tar.gz</tt>, approximately 12.2 Mo in size. ==Making the source tarball available==* access the "Sourceforge Project Admin->File Manager" page at https://sourceforge.net/projects/gramps/* create a new folder in the "Unstable" hierarchy* upload the <tt>gramps-*.tar.gz</tt> file to the new folder ==Announcing the new release==* announce on [email protected], [email protected] and [email protected]* update [[News]] if section on this is not wiki* update the list of [[previous releases]]* update reference to the new version on the [[Template:Version|wiki template]]* change the topic on the IRC channel #gramps* update the version number at [http://en.wikipedia.org/wiki/GRAMPS Wikipedia] ==Post-release==* in <tt>trunk</tt>, merge forward the case<tt>NEWS</tt> file = Guidelines for version 3.4 and before =These notes are based on version 3.4.1, released in August 2012. The steps assume a working <tt>gramps34</tt> source directory.

svn copy -r 20254 https://grampssvn.svncode.sourceforgesf.net/svnrootp/gramps/code/branches/maintenance/gramps34 https://grampssvn.svncode.sourceforgesf.net/svnrootp/gramps/code/tags/gramps-3.4.1 -m "tag 3.4.1"

svn co https://grampssvn.svncode.sourceforgesf.net/svnrootp/gramps/code/tags/gramps-3.4.1

==See also==

==External links==* http://grampssvn.svncode.sourceforgesf.net/viewvcp/gramps/code/