16,602
edits
Changes
m
cd gramps30git checkout gramps{{Stable_branch}} svn updategit pull
make See [[Translation_environment4|New environment]] and [[Talk:Translation_environment4|differences between tools]]. See also [https://github.com/gramps-project/gramps/blob/master/po/update_po.py po/update_po.py] to generate a new template/catalog (gramps.pot). python3 update_po.py -p svn git diff gramps.pot
Create Look at the changelog files: svn2cl git log v{{version}}.. --pretty --reparagraph numstat --includesummary -rev -no-authorsmerges > ChangeLog Edit and update the <tt>NEWS</tt> file.Commit the NEWS file: git commit -am "update for {{version}} release" =src=Working on VERSION== Check <tt>[https://github.com/gramps-project/datagramps/authorsblob/master/gramps/version.xmlpy gramps/version.py]</tt> to indicate an official release: cd pogedit gramps/version.py and if need, update the version for the release: svn2cl 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: -reparagraph 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: python3 Gramps.pyor python3 Gramps.py -includev ==Create a tag==Create the release tag: git tag -rev --authorsam "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 === Bump the version number in <tt>gramps/version..py</src/data/authors.xmltt> Update the version for the release: cd VERSION_TUPLE = (4, 0, ...)
Using the Revert change on <tt>Changelog<gramps/tt> files generated with <tt>svn2cl<gen/tt> in the step above, edit and update the <tt>NEWSconst.py</tt> file.Commit the NEWS file. Note the svn commit to indicate git revision number, which you'll need in the next step when you create the subversion tag: svn commit -m "update for 3.0.3 release"#VERSION += get_git_revision Committed revision 11159.+ VERSION += get_git_revision
==Subversion tag==Create a tag for the releaseSave change: svn copy -r 11159 https://gramps.svn.sourceforge.net/svnroot/gramps/branches/maintenance/gramps30 https://gramps.svn.sourceforge.net/svnroot/gramps/tags/grampsgit commit -3.0.3 -m am "tag 3.0.3bump to <new version number>" git push
Modify git checkout <tttag>configure.in-b </ttnew_branch_name> to indicate an official release: gedit configure.inThere 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=1Save these two changes. svn commit -m "make official release" configure.inNow run the following and check the version number in the "about" dialog: ./autogen.sh make python src/gramps.py
==Changelog and source tarball==Re git log v{{version}}.. --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 pretty --reparagraph numstat --includesummary -rev -no-authors=src/data/authors.xmlmerges | git2cl > ChangeLog
svn2cl git log v{{version}}.. --pretty --reparagraph numstat --includesummary --no-rev merges --authors=.*.po | git2cl > ChangeLog Using the <tt>Changelog</srctt> files generated with <tt>git2cl</datatt>, Modify <tt>MANIFEST.in</authors.xmltt> + include ChangeLog cd ..+ include po/ChangeLog
make distcheck
Note you should now have the file <tt>gramps-3.0.3.tar.gz</tt>, approximately 5.5 MB in size python3 setup.py sdist
Run Create the following steps: sftp s_charette@frs<code>readme.sourceforgerst</code> file containing the changes since the previous release.net cd uploads put gramps-3.0.3.tar.gz===Sourceforge===* access the "Sourceforge <ttProject Admin->admin</tt> tab File Manager" page at httphttps://sourceforge.net/projects/gramps/* go to or via your ''<ttdev>File Releases'' account: $ sftp <dev>@frs.sourceforge.net Connecting to frs.sourceforge.net... Password: sftp> cd /home/frs/project/gramps/tt>Stable* add create a new release folder in the <tt>"Stable</tt> package" hierarchy* fill in name, e.g., put the <tt>3readme.0.3rst</tt>* enter release notes (usually this is the text from <tt>NEWSgramps-{{version}}.tar.gz</tt>)files to the new folder ===Github===* add uploaded file(s) to the release by checking the appropriate check button and then clicking the "<tt>Add Files andAutomatically created when tagged https://or Refresh View<github.com/tt>" button* set architecture and file type, click "<tt>Updategramps-project/Refresh<gramps/tt>" releases
==See also==* [[Git|Brief introduction to SVNGit]]
==External links==* httphttps://grampsgithub.svn.sourceforge.net/viewvccom/gramps/-project
→Translation update
{{man note|Developer notes for '''What to do for a release'''}} These notes are based on version 3.0.3, released in October 2008. The steps assume a working <tt>gramps30</tt> source directory. See [[Running a development version of Gramps]] if this is not the case.=Updated guidelines for Git =
==Translation update==
Run the following steps:
cd po
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.
For checking current translation files:
python3 update_po.py -k all
==Release name==
Refer to (and update) the [[Previous releasesof Gramps|list of previous releases]] to select an appropriate name.
==Changelog and NEWS file==
==Working on the =Release from tag==Check out the new tag: cd .. svn co https://gramps.svn.sourceforge.net/svnroot/gramps/tags/gramps-3.0.3 cd gramps-3.0.3=
cd po
Create the official source tarball:
==Making the source tarball available==
==Announcing the new release==
* announce on Gramps blog
* update [[News]] section on this wiki
* update the list of [[Previous releases of Gramps|previous releases]]* update reference to the new version on the [[installationTemplate:Version|installation pagewiki template]]* update [[HeadlineNews]]
* change the topic on the IRC channel #gramps
<code> /TOPIC #gramps Welcome to Gramps! The latest versions are {{version}} 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. </code>* update the version number at [http://en.wikipedia.org/wiki/GRAMPS Gramps Wikipedia]* update mantisdb(Bug/issue database) and enable the new version via Admin:Projects item for reporting issues.
==Post-release==
* in <tt>gramps30</tt>, bump the version number in <tt>configure.in</tt>* in <tt>trunk</tt>, merge forward the <tt>NEWS</tt> file
* [[Running a development version of Gramps]]
* [[:Category:Developers/Packaging]]
* [[GrampsAIO-4 package updating]] - Updating the MS-Windows package
* http://gramps-project.org/cpanel
* http://svn.code.sf.net/p/gramps/code/
* http://sourceforge.net/projects/gramps/
[[Category:Developers/General]]
