RELEASING: Whitespace cleanup. Fix inconsistent tabbing.

This commit is contained in:
Bryce Harrington 2015-12-09 12:32:20 -08:00
parent 0986ae4dee
commit 817ae4540a

View file

@ -1,10 +1,11 @@
Here are the steps to follow to create a new cairo release:
1) Ensure that there are no local, uncommitted/unpushed
modifications. You're probably in a good state if both "git diff
HEAD" and "git log master..origin/master" give no output. Also make
sure you have libglib2.0-doc installed (else you'll get excessive
gtk-doc cross reference warnings in the next step).
1) Ensure that there are no local, uncommitted/unpushed mods.
You're probably in a good state if both "git diff
HEAD" and "git log master..origin/master" give no output. Also make
sure you have libglib2.0-doc installed (else you'll get
excessive gtk-doc cross reference warnings in the next step).
2) Verify that the code passes "make distcheck"
@ -115,8 +116,8 @@ Here are the steps to follow to create a new cairo release:
Upload the incremental ChangeLog generated by the above:
scp ChangeLog.cache-X.Y.Z-1.. \
cairographics.org:/srv/cairo.freedesktop.org/www/releases/ChangeLog.cairo-X.Y.Z
scp ChangeLog.cache-X.Y.Z-1.. \
cairographics.org:/srv/cairo.freedesktop.org/www/releases/ChangeLog.cairo-X.Y.Z
To undo a release-publish, before you've sent any emails or
pushed changes to master, delete the locally created tag (git
@ -126,36 +127,39 @@ Here are the steps to follow to create a new cairo release:
7) Update trunk (or the stable branch) version number.
For micro releases (X.Y.Z), increment cairo_version_micro to the next
larger (odd) number in cairo-version.h, commit, and push.
For micro releases (X.Y.Z), increment cairo_version_micro to the next
larger (odd) number in cairo-version.h, commit, and push.
For minor releases (X.Y.0), increment cairo_version_minor to the next
larger (odd) number, and set cairo_version_micro to 1. Then commit
and push.
For minor releases (X.Y.0), increment cairo_version_minor to the next
larger (odd) number, and set cairo_version_micro to 1. Then commit
and push.
8) Push the newly created tag out to the central tree with a command
something like:
8) Push the new tag out to the central tree with a command like:
git push origin master X.Y.Z
9) Edit the cairo bugzilla product and add the new version numbers. Note
that you need to add two versions. One for the release/snapshot (with
an even micro version), another with the post-release version (with an
odd micro version).
9) Edit the cairo bugzilla product and add the new version numbers.
10) Send a message to cairo-announce@cairographics.org and CC
cairo@cairographics.org, gnome-announce-list@gnome.org and
ftp-release@lists.freedesktop.org (pr@lwn.net as well for major
releases) to announce the new release using the text provided from
"make release-publish", adding the excerpt from NEWS, your
signature, followed by the standard "What is cairo" and "Where to
get more information about cairo" blurbs from README, and finally
the shortlog of all changes since last release, generated by:
Note that you need to add two versions. One for the
release/snapshot (with an even micro version), another with the
post-release version (with an odd micro version).
git shortlog X.Y.Z...
10) Send out an announcement message.
where X.Y.Z is the last released version.
Semd a message to cairo-announce@cairographics.org and CC
cairo@cairographics.org, gnome-announce-list@gnome.org and
ftp-release@lists.freedesktop.org (pr@lwn.net as well for major
releases) to announce the new release using the text provided from
"make release-publish", adding the excerpt from NEWS, your
signature, followed by the standard "What is cairo" and "Where to
get more information about cairo" blurbs from README, and finally
the shortlog of all changes since last release, generated by:
11) Edit the cairo wiki to add the announcement to the NEWS page and
the front page. (just the parts before your signature).
git shortlog X.Y.Z...
where X.Y.Z is the last released version.
11) Add the announcement to the NEWS page and the front page.
(just the parts before your signature).