Changes

= Guidelines Updated guidelines for version 4.0 Git = These notes are based on version 4.0.0alpha1, released in December 2012. The steps assume a working <tt>gramps40</tt> source directory.

cd gramps40git checkout gramps{{Stable_branch}} svn updategit pull

./genpot.sh # or python update_po.py -p # or intltool-update -p , .genpot.sh see [[Translation_environment4|New environment]] and [[Talk:Translation_environment4|differences between tools]] svn git diff gramps.pot

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

svn2cl git log gramps-{{version}}.. --reparagraph pretty --includenumstat -rev -summary -authors=data/authors.xml-no-merges | git2cl > ChangeLog cd po svn2cl git log gramps-{{version}}.. --pretty --numstat --reparagraph summary --includeno-rev merges --authors=po/*../datapo | git2cl > po/authors.xml cd ..ChangeLog

Using the <tt>Changelog</tt> files generated with <tt>svn2clgit2cl</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 git commit -m am "update for 4.0.0-alpha1 {{version}} release" Committed revision 20810.

Modify * 4.0.x Check <tt>setupgramps/version.py</tt> to indicate an official release: gedit setupgramps/version.py  and if need, update the version for the release: VERSION VERSION_TUPLE = "(4., 0, 2) Modify <tt>gramps/gen/const.0py</tt> to indicate an official release: - VERSION += get_git_revision(ROOT_DIR) + VERSION += "-alpha11"Save change.

Save change: svn git commit -m am "make official release" setup.py

==Subversion tag==Using the previous commit revision number, create a tag for the new release: svn copy -r 20810 https://svn* 3.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.x

==Changelog and source tarball==Modify <tt>configure.in</tt> to indicate an official release: gedit configure.inThe Changelog files There are required for two changes to make::1) Change the source tarball, but do not commit to subversionfollowing line: svn2cl -RELEASE=0.SVN$(git log -reparagraph 1 --includeformat=%h .) +dnl RELEASE=0.SVN$(git log -rev 1 --authorsformat=data/authors%h .xml):2) And change this line: cd po-dnl RELEASE=1 svn2cl +RELEASE=1Save these two changes. git commit --reparagraph --include-rev --authors=am "make official release" configure.inNow run the following and check the version number in the "about" dialog: ./data/authorsautogen.xmlsh cd .python src/gramps.py ==Create a tag==Create the official source tarballrelease tag: git tag -am "tag {{version}}" gramps-{{version}} ==Push to repository==Push the changes to the repository: python setup.py sdistgit push origin gramps-{{version}} ==Work on tag == ===Move to the new release number on branch ===

Note you should now have the file <tt>dist/gramps-* 4.0.0-alpha1.tar.gz</tt>, approximately 12.2 Mo in size.x

==Making Bump the source tarball available==* access the "Sourceforge Project Admin->File Manager" page at https://sourceforge.net/projects/gramps/* create a new folder version number in the "Unstable" hierarchy* upload the <tt>gramps-*/version.tar.gzpy</tt> file to the new folder

==Announcing Update the version for the new release: VERSION_TUPLE ==* announce on [email protected](4, 0, gramps-devel@lists.sourceforge.net and [email protected]* update [[News]] section on this 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 Revert change on <tt>trunk<gramps/gen/tt>, merge forward the <tt>NEWSconst.py</tt> fileto indicate git revision: - VERSION += "-1" + VERSION += get_git_revision(ROOT_DIR)

= Guidelines for version 3.4 and before =Save change:These notes are based on version 3.4.1, released in August 2012. The steps assume a working git commit -am "bump to <ttnew version number>gramps34</tt> source directory." git push

==Translation update==Run the following steps: cd gramps34 svn update cd po make gramps* 3.pot 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 release4.x

==Release name==Refer to (Bump the version number in <tt>configure.in</tt> and update) the [[Previous releases|list of previous releases]] to select an appropriate name<tt>src/const.py.in</tt>

==Changelog and NEWS file==Create the changelog filesSave change: svn2cl --reparagraph --include-rev --authors=src/data/authors.xml cd po svn2cl --reparagraph --include-rev -git commit -authors=../src/data/authors.xmlam "bump to <new version number>" cd ..git push

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 ===Release from tag: svn commit -m "update for 3.4.1 release" Committed revision 20254.===

==Subversion tag==Using the previous commit revision number, create a git checkout <tag 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" Committed revision 20255.b <new_branch_name>

==Working on the tag==Check out the new tag: cd .. svn co https://svn.code.sf.net/p/gramps/code/tags/gramps* Gramps-3.4.1 cd gramps-3.40.1x

Modify <tt>configureMANIFEST.in</tt> to indicate an official release: gedit configure.inThere are two changes to make::1) Change the following line: -RELEASE=0.SVN$(svnversion -n .) +dnl RELEASE=0.SVN$(svnversion -n .):2) And change this line: -dnl RELEASE=1include ChangeLog +RELEASE=1Save these two changes. svn commit -m "make official release" configure.inNow run the following and check the version number in the "about" dialog: ./autogen.sh make python srcinclude po/gramps.pyChangeLog

* upload the <tt>gramps-*{{version}}.tar.gz</tt> file to the new folder

* update the list of [[Previous releases of Gramps|previous releases]]

<pre> /TOPIC #gramps Welcome to Gramps! The latest versions are 4.1.0 and the legacy 3.4.8 || http://www.gramps-project.org/ || Please state OS and Gramps version when asking a question. Understand that replies can take up to 2 days depending on whose watching the channel. Please consider asking on the gramps-users mailing list. </pre>* update the version number at [http://en.wikipedia.org/wiki/GRAMPS Gramps Wikipedia]

* in <tt>gramps34</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

* [[Git|Brief introduction to SVNGit]]