Changes

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

=Guidelines for version 3.4 and before =Translations==These notes are based on version 3.4.1, released in August 2012. The steps assume a working <tt>gramps34</tt> source directory.

* announce the intent to release on the <tt>[email protected]</tt> mailing list; ask that no further changes be committed to svn==Translation update==* build what should be Run the final <tt>gramps.pot</tt> filefollowing steps: cd gramps34 svn update

* commit the new <tt> svn diff gramps.pot</tt> file If there have been changes, you'll need to svn* ask for all [[Translating GRAMPS|translators]] on commit <tt>gramps-users@lists.sourceforge.netpot</tt> and <tt>[email protected]</tt> to update the <tt>.po</tt> files; plan to release about 1 to 2 weeks after this date* ask for translators to e-mail update their <tt>.po</tt> files to before you; not all translators have svn access; expect to spend can make a bit of time checking in <tt>release.po</tt> files

==Preparing the tarballRelease name==Refer to (and update) the [[Previous releases|list of previous releases]] to select an appropriate name.

* edit ==Changelog and NEWS file==Create the changelog files: svn2cl --reparagraph --include-rev --authors=src/data/authors.xml cd po svn2cl --reparagraph --include-rev --authors=../src/data/authors.xml cd .. Using the <tt>Changelog</tt> files generated with <tt>ChangeLogsvn2cl</tt>* in the step above, edit and update the <tt>NEWS</tt> to add 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.4.1 release" Committed revision 20254. ==Subversion tag==Using the previous commit revision number, create a few linestag for the new release: svn copy -r 20254 https://svn.code.sf.net/p/gramps/code/branches/maintenance/gramps34 https://svn.code.sf.net/p/gramps/code/tags/gramps-3.4.1 -m "tag 3.4.1"* edit Committed revision 20255. ==Working on the tag==Check out the new tag: cd .. svn co https://svn.code.sf.net/p/gramps/code/tags/gramps-3.4.1 cd gramps-3.4.1 Modify <tt>configure.in</tt>; change to indicate an official release: gedit configure.inThere are two changes to make::1) Change the following linesline: -RELEASE=0.SVN$(svnversion -n .) dnl RELEASE=0rc1 dnl RELEASE=1:to instead say: +dnl RELEASE=0.SVN$(svnversion -n .):2) And change this line: -dnl RELEASE=0rc11 dnl +RELEASE=1* Save these two changes. svn commit -m "make official release" configure.inNow run the following commandand check the version number in the "about" dialog: ./autogen.sh make python src/gramps.py ==Changelog and source tarball==Re-create (or copy from above) the 2 Changelog files. The Changelog files are required for the source tarball, but do not commit to subversion: svn2cl --reparagraph --include-rev --authors=src/data/authors.xml cd po svn2cl --reparagraph --include-rev --authors=../src/data/authors.xml cd ..Create the official source tarball:

* login to cpanel at http://gramps-project.org/cpanel* rename Note you should now have the candidate from file <tt>gramps-23.24.x1.tar.gz</tt> to <tt>gramps-2.2.x-0rc1, approximately 9.tar6 Mo in size.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* ask people to download and test from http://gramps-project.org/test/

==Making the release source tarball available==* note the names of [[previous releases]]* upload the tarball by anonymous ftp to ftp://upload.sourceforge.net/incoming/* access the "Sourceforge Project Admin->File Manager"admin" tab page at httphttps://sourceforge.net/projects/gramps/* go to "File Releases"* add create a new release folder in the "Stable" packagehierarchy* fill in name: a number such as 2.2.8 is upload the name for sourceforge site* enter release notes -<tt>gramps- usually this is the new section of the NEWS file* add uploaded .tar.gz</tt> 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"new folder

==Once Announcing the new release is available==* announce on <tt>[email protected]</tt>, <tt>[email protected]</tt> and <tt>[email protected]</tt>

* update the list of [[previous releases]]* update reference to the new version on the [[InstallationTemplate:Version|wiki template]] page* change the topic on the IRC channel <tt>#gramps<* update the version number at [http://en.wikipedia.org/wiki/tt>GRAMPS Wikipedia]

==Update the version numberPost-release==* edit in <tt>gramps34</tt>, bump the version number in <tt>configure.in</tt>; increment the version numberand <tt>src/const.py.in</tt>* make certain the in <tt>RELEASE=1trunk</tt> line is back to , merge forward the <tt>dnl RELEASE=1NEWS</tt>* commit to svnfile

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