Commit 4eb27f3d authored by Michael Natterer's avatar Michael Natterer 😴

Bug 778285 - Release howto should contain notice to maintainers...

...of official binaries

Add this point right after "Announce on the GNOME I18N mailing list."

Also remove the "wait for mirrors" thing at the end, in a subsection
of that point we say "as fast as possible" and that contradicts each
other.

Move the "properly chilled beverage" to the end where i belongs
(or perhaps it belongs where the build starts...)
parent 96782750
......@@ -17,6 +17,10 @@
on, and how many changes to expect. An example message is:
https://mail.gnome.org/archives/gnome-i18n/2016-October/msg00035.html
( ) Also notify the maintainers of the official builds for Windows
and Mac OS of the upcoming release so they have some time to sort
out issues with their builds.
( ) If this is a stable release, make sure we have a <release> tag
inside desktop/gimp.appdata.xml.in for this upcoming version. Some
installers may feature more prominently software with recent
......@@ -144,11 +148,8 @@
update itself soon (it checks for updates every 5 minutes).
Go to https://testing.gimp.org to verify the changes.
( ) Grab a properly chilled beverage and enjoy yourself.
( ) Give the mirrors a reasonably long time to update, then announce
the release on gimp.org and send a release announcement to the
gimp-user and gimp-developer mailing lists.
( ) Announce the release on gimp.org and send a release announcement
to the gimp-user and gimp-developer mailing lists.
[ ] Check out the gimp-web master branch and merge or cherry-pick
the changes you did in the testing branch.
......@@ -160,3 +161,5 @@
[ ] Due to the tendency of news sites to front-run release
articles even before actual announcements appear, publish
everything as fast as possible.
( ) Grab a properly chilled beverage and enjoy yourself.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment