16,602
edits
Changes
m
Modify * 4.0.x Check <tt>gramps/version.py</tt> to indicate an official release:
#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 the official source tarball: python setup* 4.py sdist0.x
Note you should now have Bump the file version number in <tt>distgramps/gramps-4version.0.2.tar.gzpy</tt>, approximately 14.7 Mo in size.
==Making Update the source tarball available==* access version for the "Sourceforge Project Admin->File Manager" page at httpsrelease://sourceforge VERSION_TUPLE = (4, 0, .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]]* Revert change the topic on the IRC channel #<tt>gramps* update the version number at [http:/gen/enconst.wikipedia.orgpy</wiki/GRAMPS Wikipedia]tt> to indicate git revision: - VERSION += "-1"* announce freshmeat now known as [http://freecode.com/projects/gramps freecode], this is also a feed on the slashdot front page + VERSION += get_git_revision(ROOT_DIR)
==PostSave change: git commit -release==* am "bump the to <new version number in <tt>gramps/version.py</tt>"* in <tt>trunk</tt>, merge forward the <tt>NEWS</tt> file git push
= Guidelines for version * 3.4.0 =x
These notes are based on Bump the version 4.0number in <tt>configure.0alpha1, released in December 2012. The steps assume a working </tt> and <tt>gramps40src/const.py.in</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.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=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 tagSave change: svn git commit -m am "update for 4.0.0-alpha1 release" Committed revision 20810. ==Working on VERSION== Modify bump to <tt>new version.py</ttnumber> to indicate an official release: gedit gramps/version.py and update the version for the release:" VERSION_TUPLE = (4, 0, 0)Save change.git push
svn commit -m "make official release" gramps/version.py The version number should be the same on "about" dialog: python Gramps.py===Release from tag===
==Subversion tag==Using the previous commit revision number, create a git checkout <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.b <new_branch_name>
==Changelog and source tarball==The Changelog files are required for the source tarball, but do not commit them to subversion* Gramps-4.0.x
#Copy files from [[#Changelog and NEWS file|previous run under branch]].#Modify <tt>MANIFEST.in</tt>
Note you should now have the file <tt>dist/gramps-4.0.0.tar.gz</tt>, approximately 14.7 Mo in size. ==Making the source tarball available==* access the "Sourceforge Project AdminGramps->File Manager" page at https://sourceforge3.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==* bump the version number in <tt>gramps/version.py</tt>* in <tt>trunk</tt>, merge forward the <tt>NEWS</tt> file4
= Guidelines for version 3.4 Build, check and before =These notes are based on version 3.4.1, released in August 2012. The steps assume a working <tt>gramps34</tt> create the official source directory.tarball:
==Translation update==
Run the following steps:
cd gramps34
svn update
cd po
make gramps.pot
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=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.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.
==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> to indicate an official release:
gedit configure.in
There 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=1
Save these two changes.
svn commit -m "make official release" configure.in
Now run the following and check the version number in the "about" dialog:
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:
Note you should now have the file <tt>gramps-3.4.1.tar.gz</tt>, approximately 9.6 Mo in size.
→Changelog and NEWS file
==Translation update==
Run the following steps:
git checkout gramps40gramps{{Stable_branch}}
git pull
cd po
./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]]
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.
==Release name==
Refer to (and update) the [[Previous releasesof Gramps|list of previous releases]] to select an appropriate name.
==Changelog and NEWS file==
Create the changelog files:
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
Using the <tt>Changelog</tt> files generated with <tt>git2cl</tt> in the step above, edit and update the <tt>NEWS</tt> file.
Commit the NEWS file:
git commit -am "update for 4.0.2 {{version}} release"
==Working on VERSION==
gedit gramps/version.py
and if need, update the version for the release:
VERSION_TUPLE = (4, 0, 2)
Modify <tt>gramps/gen/const.py</tt> to indicate an official release:
- VERSION += get_git_revision(ROOT_DIR)
+ VERSION += "-1"
Save change:
git commit -am "make official release"
The version number should be the same on "about" dialog:
python Gramps.py
or
python Gramps.py -v
* 3.4.x
Modify <tt>configure.in</tt> to indicate an official release:
gedit configure.in
There are two changes to make:
:1) Change the following line:
-RELEASE=0.SVN$(git log -1 --format=%h .)
+dnl RELEASE=0.SVN$(git log -1 --format=%h .)
:2) And change this line:
-dnl RELEASE=1
+RELEASE=1
Save these two changes.
git commit -am "make official release" configure.in
Now run the following and check the version number in the "about" dialog:
./autogen.sh
python src/gramps.py
==Create a tag==
Create the release tag:
git tag -am "tag 4.0.2{{version}}" gramps-4.0.2{{version}}
==Push to repository==
Push the changes to the repository:
git push origin gramps-4.0.2{{version}}
==Changelog and source tarballWork on tag ==The Changelog files are required for the source tarball, but do not commit them to Git.
+ include ChangeLog
+ include po/ChangeLog
Create the official source tarball:
python setup.py sdist
./autogen.sh
make distcheck
==Making the source tarball available==
* 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
* create a new folder in the "Stable" hierarchy
* upload the <tt>gramps-*{{version}}.tar.gz</tt> file to the new folder
==Announcing the new release==
* 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
<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]* announce freshmeat now known as [http://freecode.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]]
