Changes between Version 8 and Version 9 of ReleaseProcess

Timestamp:

Apr 29, 2007, 12:57:26 PM (17 years ago)

Author:

nosnilmot

Comment:

--

ReleaseProcess

@@ -1 +1 @@
 = Pre Release =
  1. Commit any pending translation updates
- 2. Make sure the date and version number are correct in !ChangeLog, !ChangeLog.win32, !ChangeLog.API and po/ChangeLog
- 3. Update NEWS
- 4. Change version number at the top of configure.ac
- 5. Check pidgin.spec.in, make sure that "%define beta 7" is commented/uncommented appropriately
- 6. Make a test tarball and RPM and test to make sure everything works
+ 2. Check there are no Blocker or Critical bugs targeted for this release
+ 3. Make sure the date and version number are correct in !ChangeLog, !ChangeLog.win32, !ChangeLog.API and po/ChangeLog
+ 4. Update NEWS
+ 5. Change version number at the top of configure.ac, set version_suffix to [betaN] for betas and [] for a full release
+ 6. Check pidgin.spec.in, make sure that "%define beta 7" is commented/uncommented appropriately
+ 7. Make a test tarball and RPM and test to make sure everything works
 
 = Release =
@@ -41 +42 @@
 {{{
 rpmbuild -ba --sign --with avahi --with dbus --with meanwhile \
-    --with sasl --with silc --with tcl $rpmbuild/SPECS/gaim.spec
+    --with sasl --with silc --with tcl $rpmbuild/SPECS/pidgin.spec
 }}}
  10. Wait a few hours and let people test.
  11. Update the Pidgin website
-  a. Change inc/version.inc.php
+  a. Change inc/version.inc.php (only for full releases, not for betas)
   b. Add a news posting to htdocs/news.txt
  12. Announce via sourceforge
 
 = Post Release =
- 1. Increment version number in libpurple/version.h
+ 1. Increment version number in configure.ac & set version_suffix to [dev]
  2. Update freshmeat.net
  3. Update #pidgin topic and on-join message