16,602
edits
Changes
m
cd gramps40git checkout gramps{{Stable_branch}} svn updategit pull
python update_po.py -p # or intltool-update -p , .genpot.sh see 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}}.. --reparagraph pretty --includenumstat -rev --authors=../data/authors.xml cd po svn2cl summary --reparagraph no--include-rev --authors=data/authors.xml cd ..merges > ChangeLog
Using the <tt>Changelog</tt> files generated with <tt>svn2cl</tt> in the step above, edit Edit and update the <tt>NEWS</tt> file.Commit the NEWS file. Note the svn commit revision number, which you'll need in the next step when you create the subversion tag: svn git commit -m am "update for 4.0.0-alpha1 {{version}} release" Committed revision 20810.
Modify Check <tt>setup[https://github.com/gramps-project/gramps/blob/master/gramps/version.py gramps/version.py]</tt> to indicate an official release: gedit setupgramps/version.py and if need, update the version for the release: VERSION VERSION_TUPLE = "(4, 2, 0) Modify <tt>[https://github.com/gramps-project/gramps/blob/master/gramps/gen/const.0py#L132 gramps/gen/const.0py]</tt> to indicate an official release: -alpha1"VERSION += git_revisionSave change. + #VERSION += git_revision
python python3 Gramps.pyor python3 Gramps.py -v
==Changelog and source tarball==The Changelog files are required for Tags should be prefixed with the source tarball, but do not commit to subversion: svn2cl --reparagraph --include-rev --authors=letter v../data/authors.xml cd po svn2cl --reparagraph --include-rev --authors=data/authors.xml cd ..Create the official source tarball: python setup.py sdist
Note you should now have ==Push to repository==Push the file <tt>dist/gramps-4.0.0-alpha1.tar.gz</tt>, approximately 12.2 Mo in size.changes to the repository: git push origin v{{version}}
==Post-release==* Bump the version number in <tt>trunk<gramps/tt>, merge forward the <tt>NEWSversion.py</tt> file
= Guidelines Update the version for version 3.4 and before the release: VERSION_TUPLE =These notes are based on version 3.(4, 0, .1, released in August 2012. The steps assume a working <tt>gramps34</tt> source directory.)
==Translation update==Run the following steps: cd gramps34 svn update cd po make gramps.pot svn diff gramps.potIf there have been changes, you'll need to commit Revert change on <tt>gramps/gen/const.potpy</tt> and ask translators to update their <tt>.po</tt> files before you can make a release.indicate git revision: - #VERSION += get_git_revision + VERSION += get_git_revision
==Release name==Save change:Refer git commit -am "bump to (and update) the [[Previous releases|list of previous releases]] to select an appropriate name.<new version number>" git push
Using the git checkout <tttag>Changelog</tt> files generated with <tt>svn2cl</tt> in the step above, edit and update the <tt>NEWS-b </ttnew_branch_name> file.Commit the NEWS file. Note the svn commit revision number, which you'll need in the next step when you create the subversion tag: svn commit -m "update for 3.4.1 release" Committed revision 20254.
==Subversion tag== git log v{{version}}.. --pretty --numstat --summary --no-merges | git2cl > ChangeLogUsing the previous commit revision number, create a tag for the new release: cd po svn copy -r 20254 https://svngit log v{{version}}.code.sf.net/p/gramps/code/branches/maintenance/gramps34 https://svn.code.sf.net/p/gramps/code/tags/gramps-3.4.1 -m "tag 3.4.1" Committed revision 20255pretty --numstat --summary --no-merges -- *.po | git2cl > ChangeLog
==Working on Using the tag==Check out the new tag: cd .. svn co https://svn.code.sf.net/p/gramps/code<tt>Changelog</tagstt> files generated with <tt>git2cl</gramps-3.4.1 cd gramps-3.4.1tt>,
==Changelog and source tarball==
Re-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 --reparagraph --include-rev --authors=src/data/authors.xml
cd po
svn2cl --reparagraph --include-rev --authors=../src/data/authors.xml
cd ..
make distcheck
Note you should now have the file <tt>gramps-3.4.1.tar.gz</tt>, approximately 9.6 Mo in size python3 setup.py sdist
* http://gramps-project.org/cpanel
→Translation update
{{man note|Developer notes for '''What to do for a release '''}}= Guidelines Updated guidelines for version 4.0 Git = These notes are based on version 4.0.0alpha1, released in December 2012. The steps assume a working <tt>gramps40</tt> source directory.
==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 VERSION==
Save change: svn git add . git commit -m am "make official release" setup.py
The version number should be the same on "about" dialog:
==Subversion Create a tag==Using Create the previous commit revision number, create a release tag for the new release: svn copy git tag -r 20810 https://svn.code.sf.net/p/gramps/code/branches/maintenance/gramps40 https://svn.code.sf.net/p/gramps/code/tags/gramps-4.0.0-alpha1 -m am "tag 4.0.0 alpha1{{version}}" Committed revision 20811.v{{version}}
==Making the source tarball availableWork on tag ==* access the "Sourceforge Project Admin->File Manager" page at https://sourceforge.net/projects/gramps/* create a new folder in the "Unstable" hierarchy* upload the <tt>gramps-*.tar.gz</tt> file to the new folder
==Announcing =Move to the new releasenumber on branch ===* announce on [email protected], [email protected] and [email protected]* update [[News]] section on this wiki* update the list of [[previous releases]]* update reference to the new version on the [[Template:Version|wiki template]]* change the topic on the IRC channel #gramps* update the version number at [http://en.wikipedia.org/wiki/GRAMPS Wikipedia]
==Changelog and NEWS file=Release from tag=Create the changelog files: svn2cl --reparagraph --include-rev --authors=src/data/authors.xml cd po svn2cl --reparagraph --include-rev --authors=../src/data/authors.xml cd ..
Modify <tt>configureMANIFEST.in</tt> 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=1include ChangeLog +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 srcinclude po/gramps.pyChangeLog
Create the official source tarball:
==Making the source tarball available==
Create the <code>readme.rst</code> file containing the changes since the previous release.
===Sourceforge===
* access the "Sourceforge Project Admin->File Manager" page at https://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/gramps/Stable
* create a new folder in the "Stable" hierarchy
* upload put the <tt>readme.rst</tt> <tt>gramps-*{{version}}.tar.gz</tt> file files to the new folder ===Github===* Automatically created when tagged https://github.com/gramps-project/gramps/releases
==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 [[Template:Version|wiki 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>gramps34</tt>, bump the version number in <tt>configure.in</tt> and <tt>src/const.py.in</tt>* in <tt>trunk</tt>, merge forward the <tt>NEWS</tt> file
=See also=
* [[Git|Brief introduction to SVNGit]]
* [[Running a development version of Gramps]]
* [[:Category:Developers/Packaging]]
* [[GrampsAIO-4 package updating]] - Updating the MS-Windows package
=External links=
* https://github.com/gramps-project
* http://gramps-project.org/cpanel
* http://svn.code.sf.net/p/gramps/code/
* http://sourceforge.net/projects/gramps/
[[Category:Developers/General]]
