Changes

'''What to do for a release'''=Updated guidelines for Git =

These notes are based on a 2.2.x-based release. Specifically, these are ==Translation update==Run the notes that resulted from the release of 2.2.9 in October 2007following steps: git checkout gramps{{Stable_branch}} git pull cd po

==Translations=Gramps 4.x===For Gramps 4.x use (See [[Translation_environment4|New environment]] and [[Talk:Translation_environment4|differences between tools]]. See [https://github.com/gramps-project/gramps/blob/master/po/update_po.py po/update_po.py] to generate a new template/catalog (gramps.pot).) python update_po.py -p git 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.

===Gramps 3.4 and earlier===For Gramps 3.4 and earlier use: ./genpot.sh ==Release name==Refer to (and update) the [[Previous releases of Gramps|list of previous releases]] to select an appropriate name. ==Changelog and NEWS file==Create the changelog files: git log gramps-{{version}}.. --pretty --numstat --summary --no-merges | git2cl > ChangeLog git log gramps-{{version}}.. --pretty --numstat --summary --no-merges -- po/* announce .po | git2cl > po/ChangeLog Using the <tt>Changelog</tt> files generated with <tt>git2cl</tt> in the step above, edit and update the intent <tt>NEWS</tt> file.Commit the NEWS file: git commit -am "update for {{version}} release" ==Working on VERSION== ===Gramps 4.2.x===* 4.2.x Check <tt>[https://github.com/gramps-project/gramps/blob/master/gramps/version.py gramps/version.py]</tt> to indicate an official release on : gedit gramps/version.py  and if need, update the version for the release: VERSION_TUPLE = (4, 2, 0) Modify <tt>[https://github.com/gramps-devel@listsproject/gramps/blob/master/gramps/gen/const.sourceforgepy#L132 gramps/gen/const.netpy]</tt> mailing list; ask that no further changes be committed to svnindicate an official release: - VERSION += git_revision + #VERSION += git_revision Save change: git add . git commit -am "make official release" * build what The version number should be the final same on "about" dialog: python Gramps.pyor python Gramps.py -v ===Gramps 3.4.x===* 3.4.x Modify <tt>grampsconfigure.potin</tt> fileto indicate an official release: gedit configure.inThere 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: cd po-dnl RELEASE=1 +RELEASE=1Save these two changes. git commit -am "make official release" configure.inNow run the following and check the version number in the "about" dialog: ./autogen.sh python src/gramps.potpy ==Create a tag==Create the release tag: git tag -am "tag {{version}}" v{{version}} Tags should be prefixed with the letter v. ==Push to repository==Push the changes to the repository: git push origin v{{version}} ==Work on tag == ===Move to the new release number on branch =======Gramps 4.2.x====* commit 4.0.x Bump the new version number in <tt>gramps/version.potpy</tt> file to svn* ask Update the version for all [[Translating GRAMPS|translators]] the release: VERSION_TUPLE = (4, 0, ...) Revert change on <tt>gramps/gen/const.py</tt> to indicate git revision: - #VERSION += get_git_revision(ROOT_DIR) + VERSION += get_git_revision(ROOT_DIR) Save change: git commit -users@listsam "bump to <new version number>" git push ====Gramps 3.4.x====* 3.sourceforge4.netx Bump the version number in <tt>configure.in</tt> and <tt>gramps-devel@listssrc/const.sourceforgepy.netin</tt>  Save change: git commit -am "bump to update the <ttnew version number>" git push ===Release from tag===  git checkout <tag>.po-b </ttnew_branch_name> files; plan to release about 1 to  ====Gramps 4.2 weeks after this date.x====* ask for translators to eGramps-mail their 4.0.x Modify <tt>MANIFEST.poin</tt> files to you; not all translators have svn access; expect to spend a bit of time checking in <tt>. + include ChangeLog + include po</tt> filesChangeLog Create the official source tarball:

* edit <tt>ChangeLog</tt>* edit <tt>NEWS</tt> to add a few lines* edit <tt>configure.in</tt>; change the following lines: RELEASE=0===Gramps 3.SVN$(svnversion -n 4.) dnl RELEASEx==1:to instead say: dnl RELEASE=0.SVN$(svnversion -n .) RELEASE=1* run the following command: make distcheck* note that you should now have the <tt>grampsGramps-2.2.x.tar3.gz</tt> file4

==Making Build, check and create the candidate build available==official source tarball:

* login to cpanel at http://gramps-project.org/cpanel* rename the candidate from <tt>gramps-2.2.x.tar.gz</tt> to <tt>gramps-2.2.x-0rc1.tar .gz</tt> so everyone knows this is a release candidate* upload the candidate <tt>.tarautogen.gz</tt> file into the <tt>public_html/test/</tt> directorysh* ask people to download and test from http://gramps-project.org/test/ make distcheck

==Making the release source tarball available==* note the names of [[previous releases]]* upload the tarball by anonymous ftp to ftp://upload.sourceforge.net/incoming/* access the "Sourceforge Project Admin->File Manager"admin" tab page at httphttps://sourceforge.net/projects/gramps/* go or via your ''<dev>'' account: $ sftp <dev>@frs.sourceforge.net Connecting to "File Releases"frs.sourceforge.net... Password: sftp> cd /home/frs/project/gramps* add create a new release folder in the "Stable" packagehierarchy* fill in name: a number such as 2upload the <tt>gramps-{{version}}.2tar.8 is the name for sourceforge site* enter release notes -- usually this is the new section of the NEWS gz</tt> file* add uploaded file(s) to the release by checking the appropriate check button and then clicking the "Add Files and/or Refresh View" button* set architecture and the file type, click "Update/Refresh"new folder

==Once Announcing the new release is available==* announce on <tt>[email protected]</tt>, <tt>[email protected]</tt> and <tt>[email protected]</tt>* announce on Gramps blog

* update the list of [[Previous releases of Gramps|previous releases]]* update reference to the new version on the [[InstallationTemplate:Version|wiki template]]* update [[HeadlineNews]] page* change the topic on the IRC channel #gramps<ttcode>/TOPIC #grampsWelcome to Gramps! The latest versions are 4.2.1 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. </ttcode>* update the version number at [http://en.wikipedia.org/wiki/Gramps Wikipedia]* update mantisdb(Bug/issue database) and enable the new version for reporting issues.

==Update the version numberPost-release==* edit <tt>configure.in</tt>; increment the version number* make certain merge forward the <tt>RELEASE=1NEWS</tt> line is back to <tt>dnl RELEASE=1</tt>* commit to svnfile

==See also==* [[Git|Brief introduction to SVNGit]]

==External links==* httphttps://grampsgithub.svn.sourceforge.net/viewvccom/gramps/-project