Mailing-List: contact commits-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Mon, 07 May 2012 22:07:32 -0000
Message-ID: <20120507220732.87931.32356@eos.apache.org>
Subject: 
 =?utf-8?q?=5BCouchdb_Wiki=5D_Update_of_=22Release=5Fprocedure=22_by_NoahS?=
 =?utf-8?q?later?=
Auto-Submitted: auto-generated

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for c=
hange notification.

The "Release_procedure" page has been changed by NoahSlater:
http://wiki.apache.org/couchdb/Release_procedure?action=3Ddiff&rev1=3D115&r=
ev2=3D116

  <<Include(EditTheWiki)>>
  =

- =3D Release Procedure =3D
- =

- =3D=3D Making a Source Release =3D=3D
+ =3D Making a Source Release =3D
  =

  Any Apache CouchDB committer is free to make a source release, but they a=
re usually made by the release team.
  =

@@ -12, +10 @@

  =

  <<TableOfContents(2)>>
  =

- =3D=3D Checklist =3D=3D
+ =3D Checklist =3D
  =

   * Update the `README` file with important information.
   * Update the `NEWS` and `CHANGES` files with important information.
@@ -27, +25 @@

       * When this is set, it indicates a development version. It is set on=
 branches or on master so that the release number includes the source code =
revision number, which can be useful for development builds.
   * Update the [[Breaking_changes]] document.
  =

- =3D=3D Preparing the Community =3D=3D
+ =3D Preparing the Community =3D
  =

  Call a vote on the [[http://mail-archives.apache.org/mod_mbox/couchdb-dev=
/|couchdb-dev]] mailing list asking for a request for comments on the relea=
se. Ask all developers to specifically check the `NEWS` and `CHANGES` file =
for anything that has been added in this release.
  =

- =3D=3D Preparing the Release =3D=3D
+ =3D Preparing the Release =3D
  =

  First make sure your local repository has everything from the public repo=
sitory:
  =

@@ -86, +84 @@

  cd Y.Y.Y
  }}}
  =

- =3D=3D Release Signing =3D=3D
+ =3D Release Signing =3D
  =

  You will need a GPG key pair to sign the release.
  =

@@ -114, +112 @@

  gpg --list-keys
  }}}
  =

- =3D=3D Creating the Release Artefacts =3D=3D
+ =3D Creating the Release Artefacts =3D
  =

  To build the source for distribution you should then run the following co=
mmand:
  =

@@ -129, +127 @@

   * apache-couchdb-Y.Y.Y.tar.gz.md5
   * apache-couchdb-Y.Y.Y.tar.gz.sha
  =

- =3D=3D Checking the Release Contents =3D=3D
+ =3D Checking the Release Contents =3D
  =

  Remove any existing temporary directory:
  =

@@ -191, +189 @@

  =

  Do not upload the exported tag directory, of course. That was only for te=
sting.
  =

- =3D=3D Calling a Vote =3D=3D
+ =3D Calling a Vote =3D
  =

  Before you call the vote, you should now download your own release artefa=
cts and run the [[Test_procedure|test procedure]] with them.
  =

@@ -211, +209 @@

  =

  A vote can only pass if there are at least three +1 votes. These votes ca=
n come from anyone, including non-committers, and in fact, everyone is enco=
uraged to partake in and vote on each release. However, it is preferable th=
at at least three +1 votes come from the committers, or better yet, the PMC=
. Once three +1 votes have been counted, the vote can pass. However, if any=
one votes -1 or expresses any serious concern, that should be addressed. Us=
ually, this will be cause to abort the vote. A vote can only be closed afte=
r three working days. This allows most people a chance to test and vote on =
the release.
  =

- =3D=3D Preparing the Release Notes =3D=3D
+ =3D Preparing the Release Notes =3D
  =

  Go through the `NEWS` file and expand each bullet point as appropriate.
  =

@@ -235, +233 @@

  =

  Upload these files to `/www/www.apache.org/dist/couchdb/notes/Y.Y.Y` on `=
people.apache.org`. =

  =

- =3D=3D Making the Release =3D=3D
+ =3D Making the Release =3D
  =

  Create a signed tag:
  =

@@ -277, +275 @@

  =

  At each stage of the actual release, it is expected that a person can fol=
low the trail of changes back to the source. Because most of these systems =
are slow, things must be done in the correct order. It would be unfortunate=
 if the website listed a release that was not available on a local mirror, =
or that was missing a corresponding tag in the Git repository. The changes =
should always propagate from the source, to the `dist` directory, to the mi=
rrors, to `downloads.html`, and finally to the actual release announcement.
  =

- =3D=3D Doing Housekeeping =3D=3D
+ =3D Doing Housekeeping =3D
  =

   * Add a new release section to `NEWS` and `CHANGES` on master if not alr=
eady present.
   * Add a new release section to `NEWS` and `CHANGES` on Y.Y.x the branch =
if not already present.
@@ -292, +290 @@

   * Call a discussion on the [[http://mail-archives.apache.org/mod_mbox/co=
uchdb-dev/|couchdb-dev]] mailing list about archiving old releases.
     * To archive an old release, remove it from [[http://wiki.apache.org/c=
ouchdb/CurrentReleases|the wiki]] and then delete the corresponding directo=
ry from the `dist` directory. Do not worry about the release artefacts no l=
onger being available, they are automatically mirrored to the Apache archiv=
e site and will remain there even after they are deleted from the main `dis=
t` directory.
  =

- =3D=3D Useful Resources =3D=3D
+ =3D Useful Resources =3D
  =

   * http://www.apache.org/dev/release.html
   * http://incubator.apache.org/guides/releasemanagement.html#best-practice