summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorHavoc Pennington <hp@redhat.com>2003-09-04 16:52:03 +0000
committerHavoc Pennington <hp@src.gnome.org>2003-09-04 16:52:03 +0000
commit08ca40aad92184515820c152acebdefd62f5354e (patch)
tree4cf76ccf9570f68815dadbf14959751c4109cc1e /HACKING
parentfa4c0bf54a64a4761fe2554c09b64a4836c0ac4e (diff)
downloadmetacity-08ca40aad92184515820c152acebdefd62f5354e.tar.gz
metacity-08ca40aad92184515820c152acebdefd62f5354e.tar.bz2
2.5.5
2003-09-04 Havoc Pennington <hp@redhat.com> * configure.in: 2.5.5 * HACKING: add instructions on how to make a release
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING37
1 files changed, 37 insertions, 0 deletions
diff --git a/HACKING b/HACKING
index 013a386..d89dddb 100644
--- a/HACKING
+++ b/HACKING
@@ -1,3 +1,40 @@
+Making a release
+===
+
+To make a release of metacity, do the following:
+
+ - check out a fresh copy from CVS
+
+ - increment the version number in configure.in,
+ see the comment above the version for the next fibonacci number
+
+ - update the file NEWS based on the ChangeLog
+
+ - add a ChangeLog entry containing the version number
+ you're releasing ("Released 2.5.4" or something)
+ so people can see which changes were before and after
+ a given release.
+
+ - "make distcheck" (DO NOT just "make dist" - pass the check!)
+
+ - if make distcheck fails, fix it.
+
+ - once distcheck succeeds, "cvs commit"
+
+ - if someone else made changes and the commit fails,
+ you have to "cvs up" and run "make distcheck" again
+
+ - once the commit succeeds, WITHOUT cvs updating, "cvs tag
+ METACITY_X_Y_Z" where
+ X_Y_Z map to version X.Y.Z
+
+ - scp the tarball to master.gnome.org
+
+ - run install-module on master.gnome.org to install the tarball
+ on the ftp site
+
+Misc stuff
+===
Don't commit substantive code in here without asking me,
hp@redhat.com. Adding translations, no-brainer typo fixes, etc. is