Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
Pre Release
- Commit any pending translation updates
- Make sure the date and version number are correct in ChangeLog, ChangeLog.win32, ChangeLog.API and po/ChangeLog
- Update NEWS
- Grab the most recent FAQ from the web site
- Change version number at the top of configure.ac
- Check gaim.spec.in, make sure that "%define beta 4" is commented/uncommented appropriately
- Make a test tarball and RPM and test to make sure everything works
Release
- Tag the repository
svn copy https://svn.sourceforge.net/svnroot/gaim/trunk \
https://svn.sourceforge.net/svnroot/gaim/tags/$TAG \
-m "Tagging Gaim release $VERSION"
- Check out the tagged code
svn co https://svn.sourceforge.net/svnroot/gaim/tags/$TAG gaim
- Run ./autogen.sh
- Run make dist
- Copy gaim-$VERSION.tar.gz to a temp directory, gunzip it, then bzip2 it
- Sign the two tarballs
gpg -ab gaim-$VERSION.tar.gz
gpg -ab gaim-$VERSION.tar.bz2
gpg --verify gaim-$VERSION.tar.gz.asc gaim-$VERSION.tar.gz
gpg --verify gaim-$VERSION.tar.bz2.asc gaim-$VERSION.tar.bz2
- Build the SRPM
rpmbuild -ta --sign --with avahi --with dbus --with meanwhile \
--with sasl --with silc --with tcl gaim-$VERSION.tar.bz2
- Upload the two tarballs, the two signatures, and the src.rpm
- Make RPMs for lots of distributions and upload them
- Install the src.rpm
rpm -Uvh gaim-$VERSION-0.src.rpm
- Edit $rpmbuild/SPECS/gaim.spec and append the distro name to the end of the Release line. For example, ".fc5"
- Build
rpmbuild -ba --sign --with avahi --with dbus --with meanwhile \
--with sasl --with silc --with tcl $rpmbuild/SPECS/gaim.spec
- Wait a few hours and let people test.
- Update the Gaim website
- Change inc/version.inc.php
- Add a news posting to htdocs/news.txt
- Announce via sourceforge
Post Release
- Increment version number in libgaim/version.h
- Update freshmeat.net
Download in other formats:
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!