Changes

git checkout gramps40gramps{{Stable_branch}}

python update_po.py -p # or intltool-update -p , ===Gramps 4.genpotx===For Gramps 4.sh see x use (See [[Translation_environment4|New environment]]and [[Talk:Translation_environment4|differences between tools]]. See [https://github.com/gramps-project/gramps/blob/master/po/update_po.py po/update_po.py] to generate a new template/catalog (gramps.pot).) python update_po.py -p

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

git log gramps-4.0.1{{version}}.. --pretty --numstat --summary --no-merges | git2cl > ChangeLog git log gramps-4.0.1{{version}}.. --pretty --numstat --summary --no-merges -- po/*.po | git2cl > po/ChangeLog

git commit -am "update for 4.0.2 {{version}} release"

===Gramps 4.2.x===* 4.02.x

Modify Check <tt>[https://github.com/gramps-project/gramps/blob/master/gramps/version.py gramps/version.py]</tt> to indicate an official release:

 and if need, update the version for the release: VERSION_TUPLE = (4, 2, 0, 2) Modify <tt>[https://github.com/gramps-project/gramps/blob/master/gramps/gen/const.py#L132 gramps/gen/const.py]</tt> to indicate an official release: - VERSION += git_revision + #VERSION += git_revision 

-RELEASE=0.SVN$(svnversion git log -n 1 --format=%h .) +dnl RELEASE=0.SVN$(svnversion git log -1 -n -format=%h .)

svn git commit -m am "make official release" configure.in

git tag -am "tag 4.0.2{{version}}" gramps-4.0v{{version}} Tags should be prefixed with the letter v.2

git push origin gramps-4.0.2v{{version}}

* bump Bump the version number in <tt>gramps/version.py</tt> ===Release from tag===

Update the version for the release: git checkout <tag> -b <new_branch_name>VERSION_TUPLE = (4, 0, ...)

* Gramps -3.4Save change: ./autogen.sh make distcheck ==Changelog and source tarball==The Changelog files are required for the source tarball, but do not git commit them -am "bump to Git. * 4.0.x  #Modify <tt>MANIFEST.in</ttnew version number>" + include ChangeLog Create the official source tarball: python setup.py sdist Note you should now have the file <tt>dist/gramps-4.0.2.tar.gz</tt>, approximately 14.7 Mo in size.git push

==Making Bump the source tarball available==* access the "Sourceforge Project Admin-version number in <tt>File Manager" page at https://sourceforgeconfigure.netin</projects/gramps/* create a new folder in the "Stable" hierarchy* upload the tt> and <tt>gramps-*src/const.tarpy.gzin</tt> file to the new folder

==Announcing the new release==Save change:* announce on [email protected], [email protected] and gramps git commit -[email protected]* update [[News]] section on this wiki* update the list of [[previous releases]]* update reference am "bump 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]>"* announce freshmeat now known as [http://freecode.com/projects/gramps freecode], this is also a feed on the slashdot front page git push

==Post-release=Release from tag===* in <tt>trunk</tt>, merge forward the <tt>NEWS</tt> file

These notes are based on version ====Gramps 4.02.0alpha1, released in December 2012x====* Gramps-4. The steps assume a working <tt>gramps40</tt> source directory0.x

==Translation update==Run the following steps: cd gramps40 svn update cd po python update_po.py -p # or intltool-update -p , .genpot.sh see [[Translation_environment4|New environment]] svn diff gramps.potIf there have been changes, you'll need to commit Modify <tt>grampsMANIFEST.potin</tt> and ask translators to update their <tt>. + include ChangeLog + include po</tt> files before you can make a release.ChangeLog

==Release name==Refer to (and update) Create the [[Previous releases|list of previous releases]] to select an appropriate name.official source tarball:

==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 .python setup.py sdist

Using the <tt>Changelog</tt> files generated with <tt>svn2cl</tt> in the step above, edit and update the <tt>NEWS</tt> file====Gramps 3.Commit the NEWS file4. Note the svn commit revision number, which you'll need in the next step when you create the subversion tag:x==== svn commit * Gramps-m "update for 3.4.0.0-alpha1 release" Committed revision 20810.

Modify <tt>version .py</tt> to indicate an official release: gedit gramps/version.py and update the version for the release: VERSION_TUPLE = (4, 0, 0)Save changeautogen.sh svn commit -m "make official release" gramps/version.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 22385 https://svn.code.sf.net/p/gramps/code/branches/maintenance/gramps40 https://svn.code.sf.net/p/gramps/code/tags/gramps-4.0.0 -m "tag 4.0.0" Committed revision 22386. ==Changelog and source tarball==The Changelog files are required for the source tarball, but do not commit them to subversion. #Copy files from [[#Changelog and NEWS file|previous run under branch]].#Modify <tt>MANIFEST.in</tt> + include ChangeLog Create the official source tarball: python setup.py sdist Note you should now have the file <tt>dist/gramps-4.0.0.tar.gz</tt>, approximately 14.7 Mo in size.distcheck

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

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

<code> /TOPIC #gramps Welcome to Gramps! The latest versions are 4.2.1 and the legacy 3.4.9 || 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. </code>* update the version number at [http://en.wikipedia.org/wiki/GRAMPS Gramps Wikipedia]* announce freshmeat now known as [http:update mantisdb(Bug//freecodeissue database) and enable the new version for reporting issues.com/projects/gramps freecode], this is also a feed on the slashdot front page

* bump the version number in <tt>gramps/version.py</tt>* in <tt>trunk</tt>, merge forward the <tt>NEWS</tt> file

* [[Git|Brief introduction to SVNGit]]