GitLab

We should stop using MD5 sums altogether and push forward SHA256/SHA512
hash sums instead. The website is also being updated to display these in
favor of the deprecated MD5 sums.
We are most likely not going to remove previously computed MD5 sums, or
recompute SHA* hashes for older binaries, but at least we should stop
doing MD5 sums of any future binary.

The upper text will be centered on the top quarter of the bottom quarter
of the splash image, whereas the bottom text will be centered on the
bottom quarter of the bottom quarter of the splash (unless the splash is
too small, in which case the double of the layout pixel extents will be
used). Basically don't use absolute pixel values anymore for
positionning. This should all be done relatively since there are
nowadays all kind of display size (and positionning the text 6 pixels to
the bottom, as it was done, may be ok on low density displays, yet will
look ugly on high density screens).

Also write this down in the splash requirements in the release howto so
that splash designers are aware that the bottom quarter of their image
will have to be adapted for printing text.

Current splash is not right within these requirements. But that's all
right for this RC.
These requirements are meant to be followed from next release.

I completely forgot to rename the appstream file according to the new
ID. While doing so, I also make it a .in.in file, with initial
processing by the autotools. Indeed I need @GIMP_COMMAND@ to be replaced
by AC_CONFIG_FILES().
Finally I fix a badly closed XML tag (which reminds me I should always
test a commit, even when it's a simple non-C 1-liner change!).

Please don't forget to notify me too of an upcoming release. I need to
update the manifest (for stable releases at Flathub at least, since we
have not set the dev release process yet) and trigger a new build of our
flatpak.

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

I've made the download and home page of gimp-web as generic as possible
so that one will just have to update GIMP_VERSIONS in order to release a
new version. In particular, no boring editing of hardcoded versions in
html pages anymore.
Also adding an item to update the authors page as well (which is
generated so it's just a matter of moving a file).

...instances of GIMP before a make distcheck

Mention it in release-howto.txt.

(cherry picked from commit fef532a1)

Rename configure.in to configure.ac and update references to the
file. Configure.ac is the recomended and promoted name in the autoconf
manual.

2008-09-29  Sven Neumann  <sven@gimp.org>

	* release-howto.txt: there's no need to fiddle with
	po/Makefile.in.in these days.


svn path=/trunk/; revision=27078

2007-08-24  Raphael Quinet  <raphael@gimp.org>

	* plug-ins/jpeg/jpeg-settings.c (jpeg_swap_original_settings): new
	function that swaps the vertical and horizontal axis for the saved
	subsampling parameters and quantization tables.

	* plug-ins/jpeg/jpeg-exif.c (jpeg_exif_rotate): swap the saved
	settings when the image is rotated.  Fixes bug #466593.

	* devel-docs/release-howto.txt: added note about having admin
	access to Bugzilla and to the news section on www.gimp.org.

svn path=/trunk/; revision=23370

svn path=/trunk/; revision=23369

svn path=/trunk/; revision=23291

svn path=/trunk/; revision=23288

svn path=/trunk/; revision=23285

2007-08-16  Sven Neumann  <sven@gimp.org>

	* release-howto.txt: added a check-list for doing a GIMP 
release.


svn path=/trunk/; revision=23282