Changes

Jump to: navigation, search

What to do for a release

570 bytes added, 21:55, 2 June 2021
Add Pre-release section
Note also that [[What_to_do_for_a_release#Post-release|Post release]] there are additional things which need to be done,
which are related to making a new release, for instance making a new release-section here on the wiki, or making a new release-section on the bug tracker, or making new Debian and Mac and Windows packages, so they will need to be coordinated with the appropriate people.
 
==Pre-release==
===Agree a release timetable===
 
Co-ordinate with the package maintainers to agree a release timetable.
For a major release there may be a schedule on the [[5.2_Roadmap|Roadmap]]
 
===Announce a feature freeze===
Announce a feature freeze on the ''gramps-devel'' mailing list.
This will usually be about 4 weeks before the release date.
 
===Translation update===
The translation template should be updated, if necessary, just before the string freeze is announced.
* Check for new files since the last release:
cd po
intltool-update -m
:That will create a file called <code>missing</code>in the <code>po</code> directory if there are new files that need to be scanned for translatable strings. Examine each of the files listed in <code>missing</code>, adding each to <code>POTFILES.in</code> if it contains translatable string constants and to <code>POTFILES.skip</code> if it does not.
* Generate a new template file:
python3 update_po.py -p # makes a new gramps.pot template file
git diff gramps.pot
:Examine the changes. If they're all just comments about where a string is found you need not commit the change (so the next line will restore the official file, instead of the one you just made):
git checkout gramps.pot
:If there have been changes on <code>msgid</code> entries, you'll need to commit <code>gramps.pot</code> and ask translators to update their <tt>.po</tt> files before you can make a release:
git add gramps.pot
git commit -m "Update translation template for new release"
 
* Check current translation files (there must be no 'fatal' errors):
python3 update_po.py -k all
 
 
Also see:
* [[Template:Gramps_translations#INCOMPLETE_TRANSLATIONS]] - Update if any translation needs to be added or excluded due to not meeting the minimum 70% completion requirement.
 
===Announce a string freeze===
Announce a string freeze on the ''gramps-devel'' mailing list and on Weblate.
This will usually be about 2 weeks before the release date.
==Prepare your repository==
See also {{bug|11274}}
 
==Translation update==
* Check for new files since the last release:
cd po
intltool-update -m
:That will create a file called <code>missing</code>in the <code>po</code> directory if there are new files that need to be scanned for translatable strings. Examine each of the files listed in <code>missing</code>, adding each to <code>POTFILES.in</code> if it contains translatable string constants and to <code>POTFILES.skip</code> if it does not.
* Generate a new template file:
python3 update_po.py -p # makes a new gramps.pot template file
git diff gramps.pot
:Examine the changes. If they're all just comments about where a string is found you need not commit the change (so the next line will restore the official file, instead of the one you just made):
git checkout gramps.pot
:If there have been changes on <code>msgid</code> entries, you'll need to commit <code>gramps.pot</code> and ask translators to update their <tt>.po</tt> files before you can make a release:
git add gramps.pot
git commit -m "Update translation template for new release"
 
* Check current translation files (there must be no 'fatal' errors):
python3 update_po.py -k all
 
* if all is well, return to the root directory:
cd ..
 
 
Also see:
* [[Template:Gramps_translations#INCOMPLETE_TRANSLATIONS]] - Update if any translation needs to be added or excluded due to not meeting the minimum 70% completion requirement.
==Release name==

Navigation menu