16,602
edits
Changes
m
Create Look at the changelog files: git log gramps-4v{{version}}.0.1.. --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.
* Check <tt>[https://github.com/gramps-project/gramps/blob/master/gramps/version.py gramps/version.py]</tt> to indicate an official release: gedit gramps/version.py and if need, update the version for the release: VERSION_TUPLE = (4, 2, 0) Modify <tt>[https://github.0com/gramps-project/gramps/blob/master/gramps/gen/const.py#L132 gramps/gen/const.xpy]</tt> to indicate an official release: - VERSION += git_revision + #VERSION += git_revision
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, 2)
python python3 Gramps.py * 3.4.x Modify <tt>configure.in</tt> to indicate an official release:or gedit configurepython3 Gramps.inThere are two changes to make::1) Change the following line: -RELEASE=0.SVN$(svnversion py -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.pyv
* 4Bump the version number in <tt>gramps/version.0.xpy</tt>
bump Update the version number in <tt>gramps/versionfor the release: VERSION_TUPLE = (4, 0, ...py</tt>)
* 3Revert change on <tt>gramps/gen/const.4.xpy</tt> to indicate git revision: - #VERSION += get_git_revision + VERSION += get_git_revision
Create the official source tarball: * Gramps-4 git log v{{version}}.0.x--pretty --numstat --summary --no-merges | git2cl > ChangeLog python setupgit log v{{version}}..py sdist --pretty --numstat --summary --no-merges -- po/* Gramps-3.4 .po | git2cl > po/autogen.sh make distcheck ==Changelog and source tarball==The Changelog files are required for the source tarball, but do not commit them to Git.ChangeLog
* 4.0.x Using the <tt>Changelog</tt> files generated with <tt>git2cl</tt>,
#Modify <tt>MANIFEST.in</tt>
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.
* 3 python3 setup.4.xpy sdist
* 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 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==
* merge forward the <tt>NEWS</tt> file
= Guidelines for version 4.0 =
These notes are based on version 4.0.0alpha1, released in December 2012. The steps assume a working <tt>gramps40</tt> source directory.
==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.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.
==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>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 change.
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 Create the <ttcode>MANIFESTreadme.inrst</ttcode> + include ChangeLogfile containing the changes since the previous release.
Create the official source tarball:===Github=== python setup.py sdist* Automatically created when tagged
Note you should now have the file <tt>disthttps://github.com/gramps-4.0.0.tar.gz<project/gramps/tt>, approximately 14.7 Mo in size.releases
* http://gramps-project.org/cpanel
→Making the source tarball available
{{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
* Translations stuff python python3 update_po.py -p # or intltool-update -p , .genpot.sh see [[Translation_environment4|New environment]]
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 for 4.0.2 {{version}} release"
==Working on VERSION==
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.0.2{{version}}" gramps-4.0v{{version}} Tags should be prefixed with the letter v.2
==Push to repository==
Push the changes to the repository:
git push origin gramps-4.0.2v{{version}}
==Work on tag ==
===Move to the new release number on branch ===
Save change: git commit -am "bump the to <new version number in <tt>configure.in</tt> and <tt>src/const.py.in</tt>" git push
===Release from tag===
git checkout <tag> -b <new_branch_name>
+ include ChangeLog
+ include po/ChangeLog
Create the official source tarball:
==Making the source tarball available==
==Making the source tarball available=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 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==
* bump the version number in <tt>gramps/version.py</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
* [[:Category:AppData]] - Screenshots used by Appdata - Debian
=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]]
