2021-12-04 - Sorry the Gramps wiki is currently being upgraded to a newer software version. Please check back after the 2021-12-06.

Difference between revisions of "What to do for a release"

From Gramps
Jump to: navigation, search
(Changelog and NEWS file)
m (Announcing the new release: Added compact list of Version templates where all the Values are also visible for inspection)
 
(39 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
{{man note|Developer notes for '''What to do for a release '''}}
 
{{man note|Developer notes for '''What to do for a release '''}}
  
Note that the main use of this page will be for making
+
Note that the main use of this page will be for making a normal "minor" release.  If you are making a "major" release (e.g. x.y.0) then you will need to update this page first, to change the numbers.  But if you are only making an "alpha" or "beta" release, some steps may be skipped, or altered slightly.
a normal "minor" release.  If you are making a "major"
 
release (e.g. x.y.0) then you will need to update this
 
page first, to change the numbers.  But if you are only
 
making an "alpha" or "beta" release, some
 
steps may be skipped, or altered slightly.
 
  
Note also that [[What_to_do_for_a_release#Post-release|Post release]]
+
Note also that [[What_to_do_for_a_release#Post-release|Post release]] there are additional things which need to be done,
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.  
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.  
 
  
==Prepare your repository==
+
==Pre-release==
* Check out the current stable branch:
+
===Agree a release timetable===
  git checkout maintenance/gramps{{Stable_branch}}
+
 
:That branch name assumes that you're using the same name as the Github repository; if you're not (perhaps you don't use <code>maintenance</code> in the name) use your local name.
+
Co-ordinate with the [[Team#Package_Maintainers|package maintainers]] to agree a release timetable.
* Make sure that your local copy is clean:
+
For a major release there may be a schedule on the [[5.2_Roadmap|Roadmap]]
  git status
+
 
: If you have any uncommitted changes, either commit them now or stash them until after you've completed the release.
+
===Announce a feature freeze===
* Clean up any untracked files and make sure that the local repo is up to date:
+
For a major release, announce a feature freeze on the ''gramps-devel'' mailing list.
  git clean -fdx
+
This will usually be about 4 weeks before the release date.
  git pull --rebase
 
:If you had commits that hadn't been pushed yet they'll show up as "applying" messages in the output of this command. If that's the case re-run the tests and push as usual.
 
* Build and test to make sure that everything works, then clean the repo of all build products.
 
  
==Translation update==
+
===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:
 
* Check for new files since the last release:
 
   cd po
 
   cd po
Line 42: Line 29:
 
: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:
 
: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 add gramps.pot
   git commit -m "Update translation template for new release."
+
   git commit -m "Update translation template for new release"
  
 
* Check current translation files (there must be no 'fatal' errors):
 
* Check current translation files (there must be no 'fatal' errors):
 
   python3 update_po.py -k all
 
   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.
 +
 
 +
===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.
 +
 
 +
==Prepare your repository==
 +
* Check out the current stable branch:
 +
  git checkout maintenance/gramps{{Stable_branch}}
 +
:That branch name assumes that you're using the same name as the Github repository; if you're not (perhaps you don't use <code>maintenance</code> in the name) use your local name.
 +
* Make sure that your local copy is clean:
 +
  git status
 +
: If you have any uncommitted changes, either commit them now or stash them until after you've completed the release.
 +
* Clean up any untracked files and make sure that the local repo is up to date:
 +
  git clean -fdx
 +
  git pull --rebase
 +
:If you had commits that hadn't been pushed yet they'll show up as "applying" messages in the output of this command. If that's the case re-run the tests and push as usual.
 +
* Build and test to make sure that everything works, then clean the repo of all build products.
 +
 
 +
===Check the About box year===
 +
 
 +
Check if the year in the {{man label|About}} box needs to be updated
 +
 
 +
eg:
 +
  ''© 2007-2020 The Gramps Developers''
 +
to
 +
  ''© 2007-'''2021''' The Gramps Developers''.
 +
 
 +
Found in <code>gramps/gen/const.py</code>
 +
 
 +
===API docs update year===
 +
If needed in the file:
 +
 
 +
docs/conf.py
 +
 
 +
 
 +
Update the year for the copyright.
 +
 
 +
copyright = '2001-2019, The Gramps Project'
 +
 
 +
===Update Classifier in setup.py===
 +
Change [https://pypi.python.org/pypi?%3Aaction=list_classifiers Classifier] to the appropriate one in [https://github.com/gramps-project/gramps/blob/maintenance/gramps50/setup.py setup.py]  (master is always the first one)
 +
 
 +
<pre>
 +
Development Status :: 1 - Planning
 +
Development Status :: 2 - Pre-Alpha
 +
Development Status :: 3 - Alpha
 +
Development Status :: 4 - Beta
 +
Development Status :: 5 - Production/Stable
 +
</pre>
 +
 
 +
Check if any additional language classifier needs to be added also.
 +
 
 +
 
 +
===Update the 'behavior.betawarn' key value===
 +
 
 +
If the release is '''Production/Stable''' make sure that the '''behavior.betawarn''' key value has been set to '''False''' e.g., https://github.com/gramps-project/gramps/commit/9dc976f28dc16c514e9e8e0b0fa09338bfe04f8a#diff-3d9e6dc03ea37a4b7f7975db17f16509
 +
 
 +
Found in
 +
gramps/gen/config.py
 +
and
 +
gramps/gui/grampsgui.py
 +
 
 +
 
 +
Please note that in Gramps master this key is always '''True'''.
 +
 
 +
See also {{bug|11274}}
  
 
==Release name==
 
==Release name==
Refer to (and update) the [[Previous releases of Gramps|list of previous releases]]. Previously you needed to select an appropriate name but we have not named releases for several years now.  You will
+
Refer to (and update) the [[Previous releases of Gramps|list of previous releases]].
still need to add the release though, including things like its
+
 
relevant color.
+
Previously you needed to select an appropriate name but we have not named releases for several years now.  You will still need to add the release though, including things like its relevant color.
 +
 
 +
* [[Talk:Previous_releases_of_Gramps|Suggestions]] : For Gramps 5.0 <code>Just remember that you're standing on a planet that's evolving</code>
  
 
==Changelog and NEWS file==
 
==Changelog and NEWS file==
Line 68: Line 124:
 
Commit the NEWS file:
 
Commit the NEWS file:
 
  git add NEWS
 
  git add NEWS
  git commit -m "Update NEWS for {{version}} release"
+
  git commit -m "Update Changelog and NEWS files"
  
 
==Working on VERSION==
 
==Working on VERSION==
Line 86: Line 142:
 
* If everything looks good, push the changes:
 
* If everything looks good, push the changes:
 
   git push origin maintenance/gramps{{Stable_branch}}
 
   git push origin maintenance/gramps{{Stable_branch}}
* If that fails then someone pushed a commit while you were working. Return to [https://gramps-project.org/wiki/index.php?title=What_to_do_for_a_release#Prepare_your_repository Prepare your repository] and start over.
+
* If that fails then someone pushed a commit while you were working. Return to [[What_to_do_for_a_release#Prepare_your_repository|Prepare your repository]] and start over.
  
 
==Create a tag==
 
==Create a tag==
Line 108: Line 164:
  
 
Save change:
 
Save change:
  git commit -am "bump to <new version number>"
+
  git commit -am "Bump to <new version number>"
 
  git push
 
  git push
  
Line 115: Line 171:
 
* Go to [https://github.com/gramps-project/gramps Github] and log in if necessary.
 
* Go to [https://github.com/gramps-project/gramps Github] and log in if necessary.
 
* Select '''NN Releases''' from the line of items just above the thick line ('''NN''' is the number of releases so far).
 
* Select '''NN Releases''' from the line of items just above the thick line ('''NN''' is the number of releases so far).
* Find the tag you just pushed and click Edit.
+
* 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.
 
* Copy the NEWS file contents into the '''Write''' tab. You can use the '''Preview''' tab to check your formatting.
 
* Click '''Publish Release''' at the bottom of the edit area when you're satisfied with the contents.
 
* Click '''Publish Release''' at the bottom of the edit area when you're satisfied with the contents.
Line 123: Line 179:
 
* Click on '''Stable''' or '''Unstable''' depending on the class of the release you're making.
 
* Click on '''Stable''' or '''Unstable''' depending on the class of the release you're making.
 
* Click '''Add Folder''' and name the directory for the release version. Click "'Create'". Click your new folder to enter it.
 
* 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 locallly:
+
* You can either download the GitHub-generated tarball or create one locally:
 
   python3 setup.py sdist
 
   python3 setup.py sdist
 
* Click '''Add File''' and drag the tarball to the drop area on the web page.
 
* 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.
  
 
==Announcing the new release==
 
==Announcing the new release==
 
* update mantisdb(Bug/issue database) and enable the new version via Admin:Projects item for reporting issues. (You will need a high-enough status on the bug tracker in order to do this, so you can ask an appropriate person if you aren't.)
 
* update mantisdb(Bug/issue database) and enable the new version via Admin:Projects item for reporting issues. (You will need a high-enough status on the bug tracker in order to do this, so you can ask an appropriate person if you aren't.)
 
* announce on [email protected], [email protected] and [email protected] (You will need to be a member of all three lists first, to send to them.)
 
* announce on [email protected], [email protected] and [email protected] (You will need to be a member of all three lists first, to send to them.)
* announce on Gramps [https://gramps-project.org/introduction-WP/blog/ blog] (File under: [https://gramps-project.org/introduction-WP/category/releases/ Gramps Releases] and [https://gramps-project.org/introduction-WP/category/news/  News]) (not needed for an alpha or beta release)
+
* announce on the Discourse forum in the "[https://gramps.discourse.group/c/gramps-announce Announcements]" category.
 +
* announce on Gramps [https://gramps-project.org/blog/blog/ blog] (File under: [https://gramps-project.org/blog/category/releases/ Gramps Releases] and [https://gramps-project.org/blog/category/news/  News]) (not needed for an alpha or beta release)
 
* update [[News]] section on this wiki (not needed for an alpha or beta release)
 
* 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 the list of [[Previous releases of Gramps|previous releases]]
 
* update reference to the new version on the [[Template:Version|wiki template]] (not needed for an alpha or beta release)
 
* update reference to the new version on the [[Template:Version|wiki template]] (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 [[HeadlineNews]] (not needed for an alpha or beta release)
* change the topic on the IRC channel #gramps (not needed for an alpha or beta release)
+
* update release date on the [[Download]] page (not needed for an alpha or beta release)
<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>
+
* change the Matrix room title and IRC channel title (not needed for an alpha or beta release)
* update the version number at [http://en.wikipedia.org/wiki/Gramps Wikipedia] (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)
  
 
==Post-release==
 
==Post-release==
Line 143: Line 202:
  
 
=See also=
 
=See also=
 +
*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 packages
 +
<!--
 +
:[[File:Linux 32x32.png]]  please add link to instructions on building Gramps installers for Linux. proofed while building v5.1.3 
 +
:[[File:Beastie 32x32.png]]  please add link to instructions on building Gramps installer for BSD. proofed while building v5.1.3 
 +
:[[File:Apple logo black 32x32.png]]  please add link to instructions on building Gramps installer for Apple. proofed while building v5.1.3 
 +
-->
 
* [[Brief introduction to Git]]
 
* [[Brief introduction to Git]]
 
* [[Running a development version of Gramps]]
 
* [[Running a development version of Gramps]]
 
* [[:Category:Developers/Packaging]]
 
* [[:Category:Developers/Packaging]]
* [[GrampsAIO-4 package updating]] - Updating the MS-Windows package
 
 
* [[:Category:AppData]] - Screenshots used by Appdata - Debian
 
* [[:Category:AppData]] - Screenshots used by Appdata - Debian
 +
* [[.dtd and .rng]]
 +
* [[Rollover_for_the_manual|Rollover for the Wiki]] - for major and minor releases. No rollover for maintenance releases.
 +
* [[Special:WhatLinksHere/Template:Bug|List of pages linked to Bug Report template]] - verify the reported issues still apply to the new release. Leave links in place for any issue fixed in maintenance releases. Simply add notations for the version where the fix was applied. Remove links for fixed issues in Rollovers.
  
 
=External links=
 
=External links=
 
* https://github.com/gramps-project
 
* https://github.com/gramps-project
* http://gramps-project.org/cpanel
+
* https://gramps-project.org/cpanel
* http://sourceforge.net/projects/gramps/
+
* https://sourceforge.net/projects/gramps/
  
 
[[Category:Developers/General]]
 
[[Category:Developers/General]]

Latest revision as of 19:24, 27 July 2021

Error creating thumbnail: Unable to save thumbnail to destination
'Developer notes for What to do for a release '

Note that the main use of this page will be for making a normal "minor" release. If you are making a "major" release (e.g. x.y.0) then you will need to update this page first, to change the numbers. But if you are only making an "alpha" or "beta" release, some steps may be skipped, or altered slightly.

Note also that 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 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 missingin the po directory if there are new files that need to be scanned for translatable strings. Examine each of the files listed in missing, adding each to POTFILES.in if it contains translatable string constants and to POTFILES.skip 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 msgid entries, you'll need to commit gramps.pot and ask translators to update their .po 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:

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.

Prepare your repository

  • Check out the current stable branch:
 git checkout maintenance/gramps51
That branch name assumes that you're using the same name as the Github repository; if you're not (perhaps you don't use maintenance in the name) use your local name.
  • Make sure that your local copy is clean:
 git status
If you have any uncommitted changes, either commit them now or stash them until after you've completed the release.
  • Clean up any untracked files and make sure that the local repo is up to date:
 git clean -fdx
 git pull --rebase
If you had commits that hadn't been pushed yet they'll show up as "applying" messages in the output of this command. If that's the case re-run the tests and push as usual.
  • Build and test to make sure that everything works, then clean the repo of all build products.

Check the About box year

Check if the year in the About box needs to be updated

eg:

  © 2007-2020 The Gramps Developers 

to

  © 2007-2021 The Gramps Developers.

Found in gramps/gen/const.py

API docs update year

If needed in the file:

docs/conf.py


Update the year for the copyright.

copyright = '2001-2019, The Gramps Project'

Update Classifier in setup.py

Change Classifier to the appropriate one in setup.py (master is always the first one)

Development Status :: 1 - Planning
Development Status :: 2 - Pre-Alpha
Development Status :: 3 - Alpha
Development Status :: 4 - Beta
Development Status :: 5 - Production/Stable

Check if any additional language classifier needs to be added also.


Update the 'behavior.betawarn' key value

If the release is Production/Stable make sure that the behavior.betawarn key value has been set to False e.g., https://github.com/gramps-project/gramps/commit/9dc976f28dc16c514e9e8e0b0fa09338bfe04f8a#diff-3d9e6dc03ea37a4b7f7975db17f16509

Found in

gramps/gen/config.py

and

gramps/gui/grampsgui.py


Please note that in Gramps master this key is always True.

See also 11274

Release name

Refer to (and update) the list of previous releases.

Previously you needed to select an appropriate name but we have not named releases for several years now. You will still need to add the release though, including things like its relevant color.

  • Suggestions : For Gramps 5.0 Just remember that you're standing on a planet that's evolving

Changelog and NEWS file

Section 2a of the General Public License 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.

Note that the 5.1.4 below means the previous version, not the one you're about to release (which is the ..).

git log v5.1.4.. --pretty --numstat --summary --no-merges | git2cl > ChangeLog
git log v5.1.4.. --pretty --numstat --summary --no-merges -- po/*.po | git2cl > po/ChangeLog
git add ChangeLog
git add po/ChangeLog
  • Edit and update the NEWS file using the new ChangeLog entries as a guide. If this is the first branch in a new series there will be no NEWS file, so look at a previous release and mimic the format.

Commit the NEWS file:

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

Working on VERSION

  • Check that the VERSION_TUPLE in gramps/version.pyreflects the release you're about to make. It should if the version was bumped after the last release. If not, fix it.
- VERSION += git_revision
+ #VERSION += git_revision
  • Save the changes:
git commit -am "Release Gramps 5.1.4"
  • Check that the version number is correct:
python3 Gramps.py -v
  • If everything looks good, push the changes:
 git push origin maintenance/gramps51
  • If that fails then someone pushed a commit while you were working. Return to Prepare your repository and start over.

Create a tag

Create the release tag; note the v leading the actual tag.:

git tag -am "Tag 5.1.4" v5.1.4

Push to repository

Push the changes to the repository:

git push origin v5.1.4

Move to the new release number on branch

Bump the version number in gramps/version.py

Update the version for the release:

VERSION_TUPLE = (4, 2, ...)

Revert change on gramps/gen/const.py so that the git revision is appended to the reported version in non-release builds:

- #VERSION += get_git_revision
+ VERSION += get_git_revision

Save change:

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

Github

  • Github generates a tarball automatically when we push a tag.
  • Go to Github and log in if necessary.
  • Select NN Releases from the line of items just above the thick line (NN is the number of releases so far).
  • 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.
  • Click Publish Release at the bottom of the edit area when you're satisfied with the contents.

SourceForge

  • Go to the SourceForge files page and log in if necessary.
  • Click on Stable or Unstable depending on the class of the release you're making.
  • 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:
 python3 setup.py sdist
  • 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.

Announcing the new release

  • update mantisdb(Bug/issue database) and enable the new version via Admin:Projects item for reporting issues. (You will need a high-enough status on the bug tracker in order to do this, so you can ask an appropriate person if you aren't.)
  • announce on [email protected], [email protected] and [email protected] (You will need to be a member of all three lists first, to send to them.)
  • announce on the Discourse forum in the "Announcements" category.
  • announce on Gramps blog (File under: Gramps Releases and News) (not needed for an alpha or beta release)
  • update News section on this wiki (not needed for an alpha or beta release)
  • update the list of previous releases
  • update reference to the new version on the wiki template (not needed for an alpha or beta release)
  • Verify other "version" Wiki templates values: Last version, Stable version, etc.
  • update HeadlineNews (not needed for an alpha or beta release)
  • update release date on the Download page (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 Wikipedia (not needed for an alpha or beta release)

Post-release

  • merge forward the NEWS file

See also

  • Building a distribution to share as on the Download page
Error creating thumbnail: Unable to save thumbnail to destination
Building Gramps AIO cx freeze-based - Updating the MS-Windows 32-bit and 64-bit All-In-One packages

External links