ReleasePrep

From pgwiki

 WARNING: This page has been migrated to the PostgreSQL Wiki. Please do not edit this page or your changes may be lost!

1. Releases are performed only by community members with @postgresql.org. People known to announce releases are jdrake@postgresql.org, josh@postgresql.org and dpage@postgresql.org .

2. If the release email has a signature, make sure it is referencing PostgreSQL and not the contributors private interests.

3. Work with a web contributor or ready a patch for front page and developers/.

4. Ready email from <contributor>@postgresql.org to -general, -advocacy and -announce.

 * Check http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/catversion.h just in case it is an initdb forcing release.

5. Double check that 1,2,4 only contain references to @postgresql.org

6. Confirm packages and symlinks are on ftp sites and mirrors have begun to propagate.

7. Get confirmation from -packagers that the web patch looks good. You will need to work with your web contributor or set up a dev sandbox for this.

8. Work with operator on #postgresql to change topic. Commonly logged in operators are linuxpoet (Joshua Drake) and davidfetter (David Fetter)

9. Once 1-8 are done

 * Get web patch committed. Insure it looks correct on wwwmaster
 * Wait for patch to propagate, this takes at least one hour(site gets build every hour at exactly :00). Wait three.
   * Send announcement to -general, -advocacy and -announce
   * If you are not an -announce moderator prepare a moderator in advance. Known moderators are jd@commandprompt.com (Joshua Drake), josh@agliodbs.com (Josh Berkus) and ajs@commandprompt.com (Andrew Sullivan)

10. Update SourceForge entry (devrim@commandprompt.com)

11. Update Freshmeat (scrappy@hub.org)