mainnika/weston
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

releasing: Use version number variable

Browse Source
This commit is contained in:
Bryce Harrington
2015-05-27 13:06:59 -07:00
parent f89ca8c79d
commit bbdb2a9ba9
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
releasing.txt
+8 -8
View File
@@ -68,20 +68,20 @@ To make a release of Weston and/or Wayland, follow these steps.
Once satisfied: Once satisfied:
$ git commit releases.html -m "Add x.y.z release" $ git commit releases.html -m "Add ${RELEASE_NUMBER} release"
$ git push $ git push
$ rsync -avz * wayland.freedesktop.org:/srv/wayland.freedesktop.org/www/ $ rsync -avz * wayland.freedesktop.org:/srv/wayland.freedesktop.org/www/
8. 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 x.y branch. The x.y branch is for For x.y.0 releases, also create the release series x.y branch. The x.y
bug fixes and conservative changes to the x.y.0 release, and is where branch is for bug fixes and conservative changes to the x.y.0 release,
we release x.y.z releases from. Creating the x.y branch opens up and is where we release x.y.z releases from. Creating the x.y branch
master for new development and lets new development move on. We've opens up master for new development and lets new development move on.
done this both after the x.y.0 release (to focus development on bug We've done this both after the x.y.0 release (to focus development on
fixing for the x.y.1 release for a little longer) or before the x.y.0 bug fixing for the x.y.1 release for a little longer) or before the
release (like we did with the 1.5.0 release, to unblock master x.y.0 release (like we did with the 1.5.0 release, to unblock master
development early). development early).
$ git branch x.y $ git branch x.y