Note also that there are additional necessary [[What_to_do_for_a_release#Post-release|Post release]] there are additional things which need to be done,tasks which are related to making a new release. For instance, for instance the wiki will require making a new release-section here on and updating [[Template:Version_Templates#General|"General" version templates]]. For the wiki, or making a new release-section on the bug tracker, or . Or when making new Debian and Mac and Windows packages[[:Category:Developers/Packaging|packaging]], so they will need to be coordinated with the appropriate people[[Team#Package_Maintainers|package maintainers]] and updating the corresponding [[:Category:Versions|Versions]] : [[Template:Version_Templates|Templates]].  ==Pre-release=====Agree a release timetable=== Co-ordinate with the [[Team#Package_Maintainers|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===For a major release, 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: python 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 restore 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" 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: python update_po.py -k all:There should be very few warnings and no fatal errors. Warnings related to new languages using default values in their headers are acceptable. All 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. ===Announce a string freeze===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.

''© 2007-2018 2025 The Gramps Developers''

''© 2007-'''20192026''' The Gramps Developers''.

copyright = '2001-20192026, 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)

[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.

git commit -m "Update Changelog ChangeLog and NEWS files"

- DEV_VERSION = True + DEV_VERSION = False * Check that Add an entry to the <code>VERSION_TUPLE</code> list of releases in <code>[https://github.com/gramps-project/gramps/blob/mastermaintenance/gramps52/grampsdata/versionorg.gramps_project.Gramps.py gramps/versionmetainfo.py]</code>reflects the release you're about to makexml. It should if the version was bumped after the last releasein org. If not, fix itgramps_project. * Modify <code>[https://githubGramps.com/gramps-project/gramps/blob/master/gramps/gen/constmetainfo.py#L132 gramps/gen/constxml.pyin]</code> to indicate an official release: - VERSION += git_revision + #VERSION += git_revisionfile.

python3 python Gramps.py -v

===Move Update DEV_VERSION to the new release number on branch indicate a development version===

Bump the version number in Revert change on <code>gramps/version.pyDEV_VERSION</code> Update the version for the release: VERSION_TUPLE = (4, 2, ...) Revert change on in <code>gramps/gen/constversion.py</code> so that the git revision is appended to the reported version in non-release builds: - #VERSION +DEV_VERSION = get_git_revisionFalse + VERSION +DEV_VERSION = get_git_revisionTrue

git commit -am "Bump Set to <new development version number>"

python3 setup.py python -m build --sdist

* 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 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)* have the IRC channel admin ([[Template:Reviews/ReviewList#General|tosky]]) change the topic on the Matrix room title and IRC channel #gramps title (not needed for an alpha or beta release) <code> /TOPIC #gramps Welcome to Gramps! The latest version is {{version}} || https://www.gramps-project.org/</code>* update the version number at [httphttps://en.wikipedia.org/wiki/Gramps Gramps_(software) Wikipedia] (not needed for an alpha or beta release)

:[[File:Windows_32x32.png]] [[Building Gramps AIO cx freeze-based]] - Updating the MS-Windows 32-bit and 64-bit All-In-One packagespackage