56
edits
Changes
m
python3 python update_po.py -p # makes a new gramps.pot template file
python3 python update_po.py -k all:There should be very few warnings or and no 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.forms[Р]}".:All other fatal errors should be fixed.
python3 python Gramps.py -v
python3 setup.py python -m build --sdist
Clarify what to add in metainfo xml file
: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:
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 add gramps.pot
git commit -m "Update translation template for new release"
git push:After updating the <code>pot</code> file, push the changes and wait for Weblate to update the <code>po</code> files. Merge the corresponding pull request from Weblate.
* Check current translation files:
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.
eg:
''© 2007-2024 2025 The Gramps Developers''
to
''© 2007-'''20252026''' The Gramps Developers''.
Found in <code>gramps/gen/const.py</code>
Update the year for the copyright.
copyright = '2001-20252026, The Gramps Project'
===Update Classifier in setuppyproject.pytoml===Change [https://pypi.python.org/pypi?%3Aaction=list_classifiers Classifier] to the appropriate one in [https://github.com/gramps-project/gramps/blob/maintenance/gramps50gramps61/setuppyproject.py setuptoml pyproject.pytoml] (master is always the first one)
<pre>
==Changelog and NEWS file==
[https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html#section2 Section ''2a''] of the '''G'''eneral '''P'''ublic '''L'''icense says that if you distribute a modified version of a program: ''you must cause the modified files to carry prominent notices stating that you changed the files and the date of any change''. The change log can be generated in GNU ChangeLog format using git2cl which you may need to install on your system.
Note that the <code>{{version}}</code> below means the ''previous'' version, not the one you're about to release (which is the
Commit the NEWS file:
git add NEWS
git commit -m "Update Changelog ChangeLog and NEWS files"
==Working on VERSION==
+ DEV_VERSION = False
* Add an entry to the list of releases in [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:
* Check that the version number is correct:
* If everything looks good, push the changes:
* Click '''Add Folder''' and name the directory for the release version. Click "'Create'". Click your new folder to enter it.
* You can either download the GitHub-generated tarball or create one locally:
* Click '''Add File''' and drag the tarball to the drop area on the web page.
* Copy the release notes from GitHub into a file called README.md and upload it.
* update [[News]] section on this wiki (not needed for an alpha or beta release)
* update the list of [[Previous releases of Gramps|previous releases]]
* update reference to the new version on the [[Template:Version|wiki template]] <small>{{version}}</small> (not needed for an alpha or beta release)
* Verify other [[:Category:Versions|"version" Wiki templates]] values: Last version, Stable version, etc.
* update [[HeadlineNews]] (not needed for an alpha or beta release)
* update release <nowiki>{{version-released}}</nowiki> [https://gramps-project.org/wiki/index.php/Template:Version-released date on template] for the [[Download]] page pages <small>{{version-released}}</small> (not needed for an alpha or beta release)
* change the Matrix room title and IRC channel title (not needed for an alpha or beta release)
* update the version number at [https://en.wikipedia.org/wiki/Gramps_(software) Wikipedia] (not needed for an alpha or beta release)
*Category [[:Category:Versions|Versions]] : [[Template:Version_Templates|Template]]
*Building a distribution to share as on the [[Download]] page
:[[File:Windows_32x32.png]] [[Building Gramps AIO cx freeze-based]] - Updating the MS-Windows 32-bit and 64-bit All-In-One packagespackage
<!--
:[[File:Linux 32x32.png]] please add link to instructions on building Gramps installers for Linux. proofed while building v5.1.3