summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSimon Feltman <sfeltman@src.gnome.org>2014-02-17 17:22:40 -0800
committerSimon Feltman <sfeltman@src.gnome.org>2014-02-17 17:22:40 -0800
commitbb5550bc85ac0ff60ea39912416e347f27853fb4 (patch)
tree65318ce304b363d2c05e564147b1ed2961ff010c
parentc6ac95286bce858f1925a9d6173a91866d7e9f88 (diff)
downloadpygobject-bb5550bc85ac0ff60ea39912416e347f27853fb4.tar.gz
Update release steps to be more explicit in regards to NEWS
Add an explicit step to commit the NEWS changes and push prior tagging.
-rw-r--r--HACKING11
1 files changed, 6 insertions, 5 deletions
diff --git a/HACKING b/HACKING
index aba49858..fd8419d4 100644
--- a/HACKING
+++ b/HACKING
@@ -6,11 +6,12 @@ Making a release
3. Run make distcheck, fix any issues and commit.
4. Upload tarball: scp pygobject-3.X.Y.tar.gz master.gnome.org:
5. Install tarball: ssh master.gnome.org 'ftpadmin install pygobject-3.X.Y.tar.gz'
-6. Tag with: git tag -s 3.X.Y -m "release 3.X.Y"
-7. Push tag with: git push origin 3.X.Y
-8. Commit post-release version bump to configure.ac
-9. Send release announcements to gnome-announce-list@gnome.org; pygtk@daa.com.au; python-hackers-list@gnome.org; python-announce-list@python.org
-10. blog about it (include the HTMLized NEWS that "make release-news" prints)
+6. Commit NEWS as "release 3.X.Y" and push
+7. Tag with: git tag -s 3.X.Y -m "release 3.X.Y"
+8. Push tag with: git push origin 3.X.Y
+9. Commit post-release version bump to configure.ac
+10. Send release announcements to gnome-announce-list@gnome.org; pygtk@daa.com.au; python-hackers-list@gnome.org; python-announce-list@python.org
+11. blog about it (include the HTMLized NEWS that "make release-news" prints)
Based on http://live.gnome.org/MaintainersCorner/Releasing