summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBryce Harrington <bryce@bryceharrington.org>2016-01-20 11:50:12 -0800
committerBryce Harrington <bryce@bryceharrington.org>2016-01-20 12:37:45 -0800
commit1abf5e43b56fca493888f43e3261126b320e5cbb (patch)
tree58340957bf017d834056dc64b0ec822f2a47c989
parent51e892000ebb2298b9841b657e99def9ad188e37 (diff)
downloadweston-1abf5e43b56fca493888f43e3261126b320e5cbb.tar.gz
releasing: register_release now inserts the email announcement urls
-rw-r--r--releasing.txt11
1 files changed, 4 insertions, 7 deletions
diff --git a/releasing.txt b/releasing.txt
index fe6aa599..2467e8eb 100644
--- a/releasing.txt
+++ b/releasing.txt
@@ -58,7 +58,7 @@ To make a release of Weston and/or Wayland, follow these steps.
5. Compose the release announcements. The script will generate
- *.x.y.0.announce files with a list of changes and tags, one for
+ *.x.y.z.announce files with a list of changes and tags, one for
wayland, one for weston. Prepend these with a human-readable
listing of the most notable changes. For x.y.0 releases, indicate
the schedule for the x.y+1.0 release.
@@ -66,10 +66,7 @@ To make a release of Weston and/or Wayland, follow these steps.
6. pgp sign the the release announcements and send them to
wayland-devel@lists.freedesktop.org
- 7. Get your freshly posted release email URL from
- http://lists.freedesktop.org/archives/wayland-devel/
-
- 8. Update releases.html in wayland-web with links to tarballs and
+ 7. Update releases.html in wayland-web with links to tarballs and
the release email URL.
The register_release script in wayland-web will generate an HTML
@@ -79,11 +76,11 @@ To make a release of Weston and/or Wayland, follow these steps.
Once satisfied:
- $ git commit ./releases.html -m "Add ${RELEASE_NUMBER} release"
+ $ git commit ./releases.html -m "releases: Add ${RELEASE_NUMBER} release"
$ git push
$ ./deploy
- 9. Update topic in #wayland to point to the release announcement URL
+ 8. Update topic in #wayland to point to the release announcement URL
For x.y.0 releases, also create the release series x.y branch. The x.y
branch is for bug fixes and conservative changes to the x.y.0 release,