16,602
edits
Changes
m
python update_po.py -p # or intltool-update -p , .genpot.sh see See [[Translation_environment4|New environment]]and [[Talk:Translation_environment4|differences between tools]]. See also [https://github.com/gramps-project/gramps/blob/master/po/update_po.py po/update_po.py] to generate a new template/catalog (gramps.pot). python3 update_po.py -p
Create Look at the changelog files: git log gramps-4.0.1v{{version}}.. --pretty --numstat --summary --no-merges | git2cl > ChangeLog git log gramps-4.0.1.. --pretty --numstat --summary --no-merges -- po | git2cl > po/ChangeLog
Using the <tt>Changelog</tt> files generated with <tt>git2cl</tt> in the step above, edit Edit and update the <tt>NEWS</tt> file.
Modify Check <tt>[https://github.com/gramps-project/gramps/blob/master/gramps/version.py gramps/version.py]</tt> to indicate an official release:
python python3 Gramps.pyor python3 Gramps.py -v
#Copy files from [[#Changelog and NEWS file|previous run under ===Move to the new release number on branch]].#Modify <tt>MANIFEST.in</tt> + include ChangeLog===
Create Bump the official source tarball: python setupversion number in <tt>gramps/version.py sdist</tt>
Note you should now have Update the file <tt>dist/gramps-version for the release: VERSION_TUPLE = (4., 0, .2.tar.gz</tt>, approximately 14.7 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 "Stable" hierarchy* upload the Revert change on <tt>gramps-*/gen/const.tar.gzpy</tt> file to the new folderindicate git revision: - #VERSION += get_git_revision + VERSION += get_git_revision
==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
= Guidelines for version 4.0 = git checkout <tag> -b <new_branch_name>
These notes are based on git log v{{version 4.0}}.0alpha1, released in December 2012. The steps assume a working <tt--pretty --numstat --summary --no-merges | git2cl >gramps40</tt> source directory. ==Translation update==Run the following steps: cd gramps40 svn updateChangeLog
python update_po.py -p # or intltool-update -p , .genpot.sh see [[Translation_environment4|New environment]] svn diff grampsgit log v{{version}}.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 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 pretty --includenumstat -rev -summary -authors=data/authors.xml cd po svn2cl -no-reparagraph merges --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>version.py</ttpo | git2cl > to indicate an official release: gedit gramps/version.py and update the version for the release: VERSION_TUPLE = (4, 0, 0)Save change. svn commit -m "make official release" gramps/version.py The version number should be the same on "about" dialog: python Gramps.pyChangeLog
==Subversion tag==Using the previous commit revision number, create a tag for the new release: svn copy -r 22385 https:<tt>Changelog</tt> files generated with <tt>git2cl</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.tt>,
==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>
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 python3 setup.py sdist
= 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. ==Translation update==Run the following steps: cd gramps34 svn update cd po make gramps.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 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=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>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 3.4.1 release" Committed revision 20254. ==Subversion tag==Using the previous commit revision number, create a tag for the new release: svn copy -r 20254 https://svn.code.sfgithub.net/pcom/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. ==Working on the tag==Check out the new tag: cd .. svn co https://svn.code.sf.net/pproject/gramps/code/tags/gramps-3.4.1 cd gramps-3.4.1 Modify <tt>configure.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=1 +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 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: make distcheck Note you should now have the file <tt>gramps-3.4.1.tar.gz</tt>, approximately 9.6 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 "Stable" hierarchy* upload the <tt>gramps-*.tar.gz</tt> file to the new folderreleases
* http://gramps-project.org/cpanel
→Translation update
{{man note|Developer notes for '''What to do for a release '''}}
=Updated guidelines for Git =
==Translation update==
Run the following steps:
git checkout gramps40gramps{{Stable_branch}}
git pull
cd po
git diff gramps.pot
If 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 release.
For checking current translation files:
python3 update_po.py -k all
==Release name==
Refer to (and update) the [[Previous releasesof Gramps|list of previous releases]] to select an appropriate name.
==Changelog and NEWS file==
Commit the NEWS file:
git commit -am “update "update for 4.0.2 release”{{version}} release"
==Working on VERSION==
gedit gramps/version.py
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
Save change:
git add .
git commit -am "make official release"
The version number should be the same on "about" dialog:
==Create a tag==
Create the release tag:
git tag -am “tag 4"tag {{version}}" v{{version}} Tags should be prefixed with the letter v.0.2” gramps-4.0.2
==Push to repository==
Push the changes to the repository:
git push origin gramps-4.0.2v{{version}}
==Changelog and source tarballWork on tag ==The Changelog files are required for the source tarball, but do not commit them to Git.
==Post-release=Release from tag===* bump the version number in <tt>gramps/version.py</tt>* in <tt>trunk</tt>, merge forward the <tt>NEWS</tt> file
cd po
+ include ChangeLog
+ include po/ChangeLog
Create the official source tarball:
==Making the source tarball available==
Create the <code>readme.rst</code> file containing the changes since the previous release.
===Sourceforge===
* access the "Sourceforge Project Admin->File Manager" page at https://sourceforge.net/projects/gramps/
or via your ''<dev>'' account:
$ sftp <dev>@frs.sourceforge.net
Connecting to frs.sourceforge.net...
Password:
sftp> cd /home/frs/project/gramps/Stable
* create a new folder in the "Stable" hierarchy
* upload put the <tt>readme.rst</tt> <tt>gramps-*{{version}}.tar.gz</tt> file files to the new folder ==Announcing the new release==* announce on [email protected], [email protected] 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]* announce freshmeat now known as [http://freecode.com/projects/gramps freecode], this is also a feed on the slashdot front page
==Post-release=Github===* bump the version number in <tt>gramps/version.py</tt>* in <tt>trunk</tt>, merge forward the <tt>NEWS</tt> fileAutomatically created when tagged
==Announcing the new release==
* announce on Gramps blog
* update [[News]] section on this wiki
* update the list of [[Previous releases of Gramps|previous releases]]
* update reference to the new version on the [[Template:Version|wiki template]]
* update [[HeadlineNews]]
* change the topic on the IRC channel #gramps
<code> /TOPIC #gramps Welcome to Gramps! The latest versions are {{version}} 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 [httpupdate mantisdb(Bug/issue database) and enable the new version via Admin://freecodeProjects item for reporting issues.com/projects/gramps freecode], this is also a feed on the slashdot front page
==Post-release==
* 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
=See also=
* [[Git|Brief introduction to SVNGit]]
* [[Running a development version of Gramps]]
* [[:Category:Developers/Packaging]]
* [[GrampsAIO-4 package updating]] - Updating the MS-Windows package
=External links=
* https://github.com/gramps-project
* http://gramps-project.org/cpanel
* http://svn.code.sf.net/p/gramps/code/
* http://sourceforge.net/projects/gramps/
[[Category:Developers/General]]
