Difference between revisions of "What to do for a release"

From Gramps
Jump to: navigation, search
m (Move to the new release number on branch)
m (Working on VERSION)
Line 33: Line 33:
 
and if need, update the version for the release:
 
and if need, update the version for the release:
 
  VERSION_TUPLE = (4, 0, 2)
 
  VERSION_TUPLE = (4, 0, 2)
 +
 +
Check <tt>version.py</tt> to indicate an official release:
 +
VERSION += get_git_revision(ROOT_DIR)
 +
 
Save change:
 
Save change:
 
  git commit -am "make official release"
 
  git commit -am "make official release"

Revision as of 15:20, 27 January 2014

What to do for a release

Updated guidelines for Git

Translation update

Run the following steps:

git checkout gramps52
git pull
cd po
python update_po.py -p # or intltool-update -p , .genpot.sh see New environment
git diff gramps.pot

If there have been changes, you'll need to commit gramps.pot and ask translators to update their .po files before you can make a release.

Release name

Refer to (and update) the list of previous releases to select an appropriate name.

Changelog and NEWS file

Create the changelog files:

git log gramps-5.2.1.. --pretty --numstat --summary --no-merges | git2cl > ChangeLog
#git log gramps-5.2.1.. --pretty --numstat --summary --no-merges -- po | git2cl > po/ChangeLog
git log gramps-4.0.2.. --pretty --summary --no-merges -- po | git2cl > po/ChangeLog #4.0.2

Using the Changelog files generated with git2cl in the step above, edit and update the NEWS file. Commit the NEWS file:

git commit -am "update for 5.2.1 release"

Working on VERSION

  • 4.0.x

Check version.py to indicate an official release:

gedit gramps/version.py 

and if need, update the version for the release:

VERSION_TUPLE = (4, 0, 2)

Check version.py to indicate an official release:

VERSION += get_git_revision(ROOT_DIR)

Save change:

git commit -am "make official release"

The version number should be the same on "about" dialog:

python Gramps.py
  • 3.4.x

Modify configure.in 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
make
python src/gramps.py

Create a tag

Create the release tag:

git tag -am "tag 5.2.1" gramps-5.2.1

Push to repository

Push the changes to the repository:

git push origin gramps-5.2.1

Work on tag

Move to the new release number on branch

  • 4.0.x

bump the version number in gramps/version.py

update the version for the release:

VERSION_TUPLE = (4, 0, ...)

Save change:

git commit -am "Bump to <new version number>"
git push
  • 3.4.x

bump the version number in configure.in and src/const.py.in

Save change:

git commit -am "Bump to <new version number>"
git push

Release from tag

git checkout <tag> -b <new_branch_name>
  • Gramps-4.0.x

Modify MANIFEST.in

+ include ChangeLog

Create the official source tarball:

python setup.py sdist
  • Gramps-3.4

Build, check and create the official source tarball:

./autogen.sh
make distcheck

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 gramps-5.2.1.tar.gz file to the new folder

Announcing the new release

Post-release

  • merge forward the NEWS file

See also

External links