Open main menu

Gramps β

Changes

What to do for a release

28 bytes added, 07:34, 4 December 2016
m
move most <tt> tag to <code> tag
git log v{{version}}..
Edit and update the <ttcode>NEWS</ttcode> file.
Commit the NEWS file:
git commit -am "update for {{version}} release"
git commit -am "Update ChangeLog files"
The <ttcode>Changelog</ttcode> files generated with <code>git2cl</code>.
Will be also included on tarball generated by [[#Github|Github]].
VERSION_TUPLE = (4, 0, ...)
Revert change on <ttcode>gramps/gen/const.py</ttcode> to indicate git revision:
- #VERSION += get_git_revision
+ VERSION += get_git_revision
git checkout <tag> -b <new_branch_name>
Modify <ttcode>MANIFEST.in</ttcode>
+ include ChangeLog
+ include po/ChangeLog
sftp> cd /home/frs/project/gramps/Stable
* create a new folder in the "Stable" hierarchy
* put the <ttcode>readme.rst</ttcode> <ttcode>gramps-{{version}}.tar.gz</ttcode> files to the new folder
==Announcing the new release==
==Post-release==
* merge forward the <ttcode>NEWS</ttcode> file
=See also=