Changes

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

These notes are based ==Translation update==Run the following steps: git checkout gramps{{Stable_branch}} git pull cd po ===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/*.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 {{version}} release" ==Working on a VERSION== ===Gramps 4.2.x===* 4.2.x Check <tt>[https://github.com/gramps-based project/gramps/blob/master/gramps/version.py gramps/version.py]</tt> to indicate an official release: gedit gramps/version. Specificallypy  and if need, these are update the notes that resulted from version for the release of : VERSION_TUPLE = (4, 2, 0) Modify <tt>[https://github.com/gramps-project/gramps/blob/master/gramps/gen/const.py#L132 gramps/gen/const.py]</tt> to indicate an official release: - VERSION += git_revision + #VERSION += git_revision Save change: git add . git commit -am "make official release" The version number should be the same on "about" dialog: python Gramps.pyor python Gramps.py -v ===Gramps 3.4.x===* 3.4.x Modify <tt>configure.in</tt> to 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: -dnl RELEASE=1 +RELEASE=1Save these two changes. git commit -am "make official release" configure.9 in October 2007Now 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 {{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}}

==TranslationsWork on tag ==

* announce ===Move to the intent to new release number on the gramps-devel@listsbranch =======Gramps 4.sourceforge2.net mailing list; ask that no further changes be committed to svnx====* build what should be 4.0.x Bump the last version number in <tt>gramps/version.potpy</tt> file Update the version for the release: cd poVERSION_TUPLE = (4, 0, ...) make gramps.pot* commit the new Revert change on <tt>gramps/gen/const.potpy</tt> file to svnindicate git revision: - #VERSION += get_git_revision(ROOT_DIR) + VERSION += get_git_revision(ROOT_DIR) Save change:* ask for all [[Translating GRAMPS|translators]] on gramps git commit -users@listsam "bump to <new version number>" git push ====Gramps 3.sourceforge4.net and gramps-devel@listsx====* 3.sourceforge4.net to update x Bump the version number in <tt>configure.poin</tt> files; plan to release about 1 to 2 weeks after this date* ask for translators to e-mail their and <tt>src/const.py.poin</tt> files  Save change: git commit -am "bump to you; not all translators have svn access; expect to spend a bit of time checking in <new version number>" git push ===Release from tag===  git checkout <tag> -b <new_branch_name> ====Gramps 4.2.x====* Gramps-4.0.x Modify <tt>MANIFEST.poin</tt> files + include ChangeLog + include po/ChangeLog Create the official source tarball:  python setup.py sdist ====Gramps 3.4.x====* Gramps-3.4

==Preparing Build, check and 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.SVN$(svnversion -n autogen.) dnl RELEASE=1:to instead say: dnl RELEASE=0.SVN$(svnversion -n .) RELEASE=1* run the following command:sh

==Making the source tarball available==* login to cpanel access the "Sourceforge Project Admin->File Manager" page at httphttps://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.org/cpanelgramps* create a new folder in the "Stable" hierarchy* upload the candidate <tt>gramps-{{version}}.tar.gz</tt> file into to the <tt>public_html/test/</tt> directory* ask people to download and test from http://gramps-project.org/test/new folder

==When Announcing the candidate is ready to be releasednew release==* access the Sourceforge "admin" tab at http://announce on [email protected], gramps-devel@lists.sourceforge.net/projects/and gramps/[email protected]* go to "File Releases"announce on Gramps blog* add a new release in the "Stable" packageupdate [[News]] section on this wiki* note update the names list of [[Previous releases of Gramps|previous releases]]* upload update reference to the new version on the [[Template:Version|wiki template]]* update [[HeadlineNews]]* change the topic on the tarball by anonymous ftp IRC channel #gramps<code> /TOPIC #gramps Welcome to ftpGramps! The latest versions are 4.2.1 and the legacy 3.4.9 || http://uploadwww.sourceforgegramps-project.netorg/incoming/* announce || 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-announce@listsusers mailing list.sourceforge.net, as well as devel and user list</code>:* update news section on this the version number at [http://en.wikipedia.org/wiki/Gramps Wikipedia]:* change reference from old to update mantisdb(Bug/issue database) and enable the new version on the [[Installation]] pagefor 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