callisto-debian/gtk3
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updates

Browse Source 
svn path=/trunk/; revision=20312
This commit is contained in:
Matthias Clasen 2008-06-04 03:28:55 +00:00
parent 7b46a3a2ec
commit 1e5192fd1c
2 changed files with 87 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog
View File

@ -1,3 +1,7 @@
2008-06-03 Matthias Clasen <mclasen@redhat.com>
* docs/RELEASE-HOWTO: Update a bit
2008-06-03 Matthias Clasen <mclasen@redhat.com> 2008-06-03 Matthias Clasen <mclasen@redhat.com>
* configure.in: Bump version * configure.in: Bump version

111
docs/RELEASE-HOWTO
View File

@ -1,45 +1,92 @@
How to do a GTK+ release? How to do a GTK+ release?
========================= =========================
Make sure you have Owen's special autoconf and libtool RPMs, available at: Make sure you have suitable versions of autoconf and libtool.
http://people.redhat.com/otaylor/gtk/autotools/.
Also make sure you have the following packages installed with all their Also make sure you have the following packages installed with all their
dependencies (I used the RPM package names from RedHat 9): dependencies:
* gtk-doc * gtk-doc
* linuxdoc-tools
* docbook-utils * docbook-utils
Without those packages make distcheck will *not* pass. Without those packages make distcheck will *not* pass.
0) Blow away your gtk+ directory, check a new version out 0) Blow away your gtk+ directory, check a new version out
1) autogen and build it, make sure to enable docs.
2) Update NEWS based on the various ChangeLog files 1) autogen and build it, make sure to enable docs by specifying
--enable-gtk-doc --enable-man
2) Update NEWS based on the various ChangeLog files; follow the format
of prior entries. This includes finding noteworthy new features,
collecting summaries for all the fixed bugs that are referenced
and collecting all updated translations.
Also collect the names of all contributors that are mentioned.
We don't discriminate between bug reporters, patch writers,
committers, etc. Anybody who is mentioned in ChangeLog gets
credits, but only real names, not email addresses or nicknames.
3) Verify that the version in configure.in has been bumped after the last 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 release. (Note that this is critical, a slip-up here will cause the
to change). soname to change).
4) Make sure that make check is happy (If you don't do it here, make distcheck 4) Make sure that make check is happy (If you don't do it here, make distcheck
will also catch it, but it is kind of disheartening to see make distcheck fail will also catch it, but it is kind of disheartening to see make distcheck
due to an extraneous symbol after watching it build the docs for an hour...) fail due to an extraneous symbol after watching it build the docs for an
5) Add === Released 2.x.y === at the top of all ChangeLog files hour...).
6) make distcheck Typical problems to expect here (depending on whether this is a devel
7) Fix broken stuff found by 5) repeat snapshot or a stable release):
8) cvs commit; you'll have a bunch of po file changes, and maybe some * forgotten source files
doc changes too (NOTE: be sure to use cvs with compression, else you'll * new symbols missing from .symbols files
end up waiting for a long time :). * symbols that are exported by should be private (static or _-prefixed)
9) If 7) fails because someone else committed inbetween, curse, cvs up,
fix conflicts and go to 5) 5) If this is a devel release, make sure that the docs for new symbols
10) type 'cvs tag GTK_2_x_y' in the toplevel directory are in good shape. Look at the -unused.txt files and add stuff found
11) You now have the tarball, and the CVS tag, now upload the tarball to there to the corresponding -sections.txt file. Make sure that all
gnome.org and gtk.org new symbols have proper Since: tags, and that there is an index
12) Go to the gnome-announce list archives, find the last announce message, in the main -docs.sgml for the next stable version.
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. 6) Add === Released 2.x.y === at the top of all ChangeLog files
13) Send it to gnome-announce-list, gtk-list, gtk-app-devel-list and
7) make distcheck
8) Fix broken stuff found by 7), repeat
9) svn commit; you'll have a bunch of po file changes, ChangeLog updates,
and maybe some doc changes too
10) If 7) fails because someone else committed inbetween, curse, svn up,
fix conflicts and go to 7)
11) Now you've got the tarball. Check that the tarball size looks
reasonable compared to previous releases. If the size goes down
a lot, likely the docs went missing for some reason. If the size
goes up by a lot, something else may be wrong.
11) Tag the release. The command for doing that looks like
svn cp svn+ssh://matthiasc@svn.gnome.org/svn/gtk+/branches/gtk-2-12 \
svn+ssh://matthiasc@svn.gnome.org/svn/gtk+/tags/GTK_2_12_10
12) Bump the version number in configure.in and commit this change
with a ChangeLog entry
13) Upload the tarball to master.gnome.org and run install-module to transfer
it to download.gnome.org. If you don't have an account on master.gnome.org,
find someone who can do it for you. The command for this looks like
scp gtk+-2.12.10.tar.gz matthiasc@master.gnome.org:
ssh matthiasc@master.gnome.org
install-module gtk+-2.12.10.tar.gz
14) Get the bz2 tarball and the .md5sum files back from master.gnome.org
You can probably also create it locally, but I've experienced md5
mismatches when doing so
15) 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.
16) Send it to gnome-announce-list, gtk-list, gtk-app-devel-list and
gtk-devel-list. Set reply-to to gnome-hackers. gtk-devel-list. Set reply-to to gnome-hackers.
14) Bump the version number in configure.in.
15) Create a new milestone in bugzilla and move the remaining bugs from the 17) Add a link to the release announcement to www.gtk.org which lives
2.x.y milestone over to the new one. in the gtk-web cvs module.
16) Add a link to the release announcement to www.gtk.org which lives in
the gtk-web cvs module.