915
edits
Changes
→Github
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
:There should be very few warnings or fatal errors. Warnings related to new languages using default values in their headers are acceptable. There will also be some fatal errors reported due to the non-standard way we handle inflected dates. See the section on [https://gramps-project.org/wiki/index.php/Date_Handler#Localizing_the_date_formats Localizing the date formats] in the [https://gramps-project.org/wiki/index.php/Date_Handler Date Handler] wiki page for further details. For example "{long_month}" may be translated as "{long_month.f[Р]}".:All other fatal errors should be fixed.
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.
For a major release, announce a string freeze on the ''gramps-devel'' mailing list and on Weblate.
This will usually be about 2 weeks before the release date.
In the ''Program'' component on Weblate, select "Manage⟶Post announcement" from the menu. Enter an ''Expiry date'' the day before the release date, and select the ''Notify users'' checkbox to send a notification to all subscribed users.
==Prepare your repository==
eg:
''© 2007-2021 2023 The Gramps Developers''
to
''© 2007-'''20222024''' The Gramps Developers''.
Found in <code>gramps/gen/const.py</code>
Update the year for the copyright.
copyright = '2001-20222024, The Gramps Project'
===Update Classifier in setup.py===
Check if any additional language classifier needs to be added also.
==Release name==
* Check that the <code>VERSION_TUPLE</code> reflects the release you're about to make. It should if the version was bumped after the last release. If not, fix it.
* Add an entry to the [https://github.com/gramps-project/gramps/blob/maintenance/gramps52/data/org.gramps_project.Gramps.metainfo.xml.in org.gramps_project.Gramps.metainfo.xml.in] file.
* Save the changes:
* Find the tag you just pushed and click it, or click the "Draft a new release" button.
* Copy the NEWS file contents into the '''Write''' tab. You can use the '''Preview''' tab to check your formatting.
* Add the sh256sum of the source distribution to the bottom of the release notes.
You can obtain the sha256sum with the following command:
git archive --format=tar --prefix=gramps-{{version}} v{{version}} | gzip | sha256sum
Alternatively, download it and use:
sha256sum gramps-{{version}}.tar.gz
* Click '''Publish Release''' at the bottom of the edit area when you're satisfied with the contents.