From 09951ec9ad92e400abb7662140f712f417433dcc Mon Sep 17 00:00:00 2001 From: Kristian Rietveld Date: Mon, 18 Nov 2002 23:34:02 +0000 Subject: new file describing the release process. Tue Nov 19 00:45:34 2002 Kristian Rietveld * docs/RELEASE-HOWTO: new file describing the release process. * docs/Makefile.am: added RELEASE-HOWTO to EXTRA_DIST. --- docs/RELEASE-HOWTO | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 docs/RELEASE-HOWTO (limited to 'docs/RELEASE-HOWTO') diff --git a/docs/RELEASE-HOWTO b/docs/RELEASE-HOWTO new file mode 100644 index 0000000000..b4826e1691 --- /dev/null +++ b/docs/RELEASE-HOWTO @@ -0,0 +1,27 @@ +How to do a GTK+ release? +========================= + +Make sure you have Owen's special autoconf and libtool RPMs, available at: +http://people.redhat.com/otaylor/gtk/autotools/ + + +0) Blow away your gtk+ directory, check a new version out +1) Update NEWS based on ChangeLog +2) Update version in configure.in, increase MICRO, interface and binary +age by 1. (Note that this is critical, a slip-up here will cause the soname +to change). +3) Add === Released 2.0.9 === at the top of the ChangeLog +4) make distcheck +5) Fix broken stuff found by 4) repeat +6) cvs commit; you'll have a bunch of po file changes, and maybe some +doc changes too +7) If 6) fails because someone else committed inbetween, curse, cvs up +fix conflicts and go to 4) +8) type 'cvs tag GTK_2_0_9' in the toplevel directory +9) You now have the tarball, and the CVS tag, now upload the tarball to +gnome.org and gtk.org +10) Go to the gnome-announce list archives, find the last announce message, +create a new message in the same form, replacing version numbers, commentary +at the top about "what this release is about" and the Summary of changes. +11) Send it to gnome-announce-list, gtk-list, gtk-app-devel-list and +gtk-devel-list. -- cgit v1.2.1