gimp-help 2.10.34 release tracker
This issue will track the status of the preparations for the 2.10.34 release of gimp-help.
Checklist for release:
-
Announce a string freeze on GNOME discourse with the gimp
andi18n
tags: https://discourse.gnome.org/t/gimp-help-manual-2-10-34-release-planned/14016It serves as an announcement to both developers and translators.
Mention:
- the planned release version;
- the frozen branch name;
- the expected release date (end of freeze) (plan for a couple of weeks at least. No translatable strings must be touched during this time);
- this bug report URL.
-
Check that you have working SSH access to master.gnome.org
and that you are a member of thegimpftpadmin
group. If not, ask Michael Natterer, Michael Schumacher or Jehan for assistance. -
Check that master.gnome.org
has enough space to upload the release and to place it into the download area. If not, make place or ask Michael Natterer, Michael Schumacher or Jehan to do that. -
Check that you have admin access to gimp-help
module on Gitlab and commit access to thegimp-web
module, or that someone can do the changes for you. -
Check if NEWS
,stylesheets/authors.xml
(and the generatedAUTHORS
),README.md
or anything else needs to be updated. -
Check our Continuous Integration builds: all jobs must be successful because we should not release with code validation or installer build errors. The following procedure simulates a release:
-
Create a pipeline: choose the branch we plan to release and add the variable CI_COMMIT_TAG
to any value (it will simulate a build with a tag, which is characteristic of a release). -
Besides the normal jobs, the following builds should be triggered -
distcheck-1
anddistcheck-2
, these check that make dist works. With a 2-hour runner timeout, we have to split this into two parts. -
source-dist
, builds the source tarball. This should result in a tarball and two checksum files.
-
-
Check in particular: -
distcheck-1
anddistcheck-2
, should not fail. -
source-dist
, should result in a tarball and two checksum files. -
win-installer
should have Windows installers for all available languages and two checksum files.
-
If these steps work fine, we are ready to tag and publish.
Note: the test build will likely take more than 1 hour, especially because of the distcheck step. And of course, if you ever discover any build or run into issues, the time will be multiplied. It is advised to take this in consideration. This test step should be run well in advance, even the day before.
-
-
Bump the version number in configure.ac
to the same version as the corresponding GIMP release. -
Commit the version bumps only and push. Since there was no code change since the last CI check, the CI should build fine once again. Make sure of it. -
Tag the release and push the tag: git tag -s GIMP_HELP_2_x_y -m 'release 2.x.y' git push origin GIMP_HELP_2_x_y
All release tags are signed in order for the authenticity and origin of the release to be publicly verified.
-
Wait for the CI to finish the build, then ask ender to sign the installers. -
Find someone to upload all files as mentioned above, and wait for that to be done. -
Update gimp-help website. -
Let other's check the news item for the website and update where necessary. -
Publish the news by merging testing into master. -
Publish news on social media. -
After release: update LAST_RELEASE_TAG
inMakefile.am
and bump the version number inconfigure.ac
.