* gtk-doc
* docbook-utils
Without those packages make distcheck will *not* pass.
+Make sure that gtk-doc is the latest released version.
0) Go back to a pristine working directory. With git, this works:
committers, etc. Anybody who is mentioned in ChangeLog gets
credits, but only real names, not email addresses or nicknames.
- 3) In particular, if this is a major, stable, release, verify that
+ 3) Update the pot files and commit the changes:
+
+ make -C po gtk30.pot
+ make -C po-properties gtk30-properties.pot
+
+ 4) In particular, if this is a major, stable, release, verify that
README.in contains the relevant release notes and that the
required versions of dependencies in INSTALL.in are in sync
- with configure.in.
+ with configure.ac.
- 4) Verify that the version in configure.in has been bumped after the last
+ 5) Verify that the version in configure.ac has been bumped after the last
release. (Note that this is critical, a slip-up here will cause the
soname to change).
- 5) Make sure that make check is happy (If you don't do it here, make distcheck
+ 6) 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 due to an extraneous symbol after watching it build the docs for an
hour...).
using a function from a different library, which is not yet allowed
by the filter in pltcheck.sh
- 6) If this is a devel release, make sure that the docs for new symbols
+ 7) If this is a devel release, make sure that the docs for new symbols
are in good shape. Look at the -unused.txt files and add stuff found
there to the corresponding -sections.txt file. Look at the
-undocumented.txt files and see if there is anything in there that
Since: tags, and that there is an index in the main -docs.sgml for
the next stable version.
- 7) make distcheck
+ 8) make distcheck
- 8) Fix broken stuff found by 7), repeat
+ 9) Fix broken stuff found by 8), commit changes: git commit -a, repeat.
- 9) Commit all changes: git commit -a. You will have a bunch of po file
- changes, NEWS and maybe some doc changes too
+10) Once distcheck succeeds, verify that the tree is clean: git diff should
+ come up empty.
10) Now you've got the tarball. Check that the tarball size looks
reasonable compared to previous releases. If the size goes down
git push origin refs/tags/2.12.10
-13) Bump the version number in configure.in and commit and push this change
+13) Bump the version number in configure.ac and commit and push this change
14) 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
-
-15) 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.
+ scp gtk+-2.12.10.tar.xz matthiasc@master.gnome.org:
+ ssh matthiasc@master.gnome.org ftpadmin install gtk+-2.12.10.tar.xz
-16) Upload the .gz and .bz2 tarballs and checksums to ftp.gtk.org and put
- them in the right directory below /ftp/pub. Pay attention to correct
- ownership, and don't forget to update the LATEST file in the directory.
+15) Upload the tarball and checksum to ftp.gtk.org and put them in the right
+ directory below /ftp/pub. Pay attention to correct ownership, and don't
+ forget to update the LATEST file in the directory.
-17) Go to the gnome-announce list archives, find the last announce message,
+16) 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.
-18) Send it to gnome-announce-list, gtk-list, gtk-app-devel-list and
- gtk-devel-list. Set reply-to to gnome-hackers.
+17) Send it to gnome-announce-list, gtk-list, gtk-app-devel-list and
+ gtk-devel-list. Set reply-to to desktop-devel-list.
-19) Add a link to the release announcement to www.gtk.org which lives
- in the gtk-web cvs module.
+18) Add a link to the release announcement to www.gtk.org which lives
+ in the gtk-web git module.
projects / ~andy / gtk / blobdiff