2002-11-18 23:34:02 +00:00
|
|
|
How to do a GTK+ release?
|
|
|
|
|
=========================
|
|
|
|
|
|
|
|
|
|
Make sure you have Owen's special autoconf and libtool RPMs, available at:
|
2002-11-20 21:55:05 +00:00
|
|
|
http://people.redhat.com/otaylor/gtk/autotools/.
|
|
|
|
|
|
2003-09-04 17:16:53 +00:00
|
|
|
Also make sure you have the following packages installed with all their
|
|
|
|
|
dependencies (I used the RPM package names from RedHat 9):
|
2002-11-20 21:55:05 +00:00
|
|
|
* gtk-doc
|
|
|
|
|
* linuxdoc-tools
|
|
|
|
|
* docbook-utils
|
|
|
|
|
|
|
|
|
|
Without those packages make distcheck will *not* pass.
|
2002-11-18 23:34:02 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
0) Blow away your gtk+ directory, check a new version out
|
2002-11-20 21:55:05 +00:00
|
|
|
1) autogen and build it, make sure to enable docs.
|
2004-04-30 16:34:36 +00:00
|
|
|
2) Update NEWS based on the various ChangeLog files
|
2004-05-06 13:38:02 +00:00
|
|
|
3) Verify that the version in configure.in has been bumped after the last
|
|
|
|
|
release. (Note that this is critical, a slip-up here will cause the soname
|
|
|
|
|
to change).
|
2004-04-30 16:34:36 +00:00
|
|
|
4) Add === Released 2.x.y === at the top of all ChangeLog files
|
|
|
|
|
5) make distcheck
|
|
|
|
|
6) Fix broken stuff found by 5) repeat
|
2002-11-20 21:55:05 +00:00
|
|
|
7) cvs commit; you'll have a bunch of po file changes, and maybe some
|
|
|
|
|
doc changes too (NOTE: be sure to use cvs with compression, else you'll
|
|
|
|
|
end up waiting for a long time :).
|
2004-04-30 16:34:36 +00:00
|
|
|
8) If 7) fails because someone else committed inbetween, curse, cvs up,
|
2002-11-20 21:55:05 +00:00
|
|
|
fix conflicts and go to 5)
|
2003-09-04 17:16:53 +00:00
|
|
|
9) type 'cvs tag GTK_2_x_y' in the toplevel directory
|
2002-11-20 21:55:05 +00:00
|
|
|
10) You now have the tarball, and the CVS tag, now upload the tarball to
|
2002-11-18 23:34:02 +00:00
|
|
|
gnome.org and gtk.org
|
2002-11-20 21:55:05 +00:00
|
|
|
11) Go to the gnome-announce list archives, find the last announce message,
|
2002-11-18 23:34:02 +00:00
|
|
|
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.
|
2002-11-20 21:55:05 +00:00
|
|
|
12) Send it to gnome-announce-list, gtk-list, gtk-app-devel-list and
|
|
|
|
|
gtk-devel-list. Set reply-to to gnome-hackers.
|
2004-05-06 13:38:02 +00:00
|
|
|
13) Bump the version number in configure.in.
|
2004-07-10 05:36:06 +00:00
|
|
|
14) Create a new milestone in bugzilla and move the remaining bugs from the
|
|
|
|
|
2.x.y milestone over to the new one.
|
|
|
|
|
15) Add a link to the release announcement to www.gtk.org which lives in
|
|
|
|
|
the gtk-web cvs module.
|
