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: Thu, 05 Apr 2012 22:30:36 -0000
Message-ID: <20120405223036.49246.42208@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=3D108&r=
ev2=3D109

   * Publish a blog post using the HTML version of the release notes.
   * Send the [[http://mail-archives.apache.org/mod_mbox/www-announce/20100=
7.mbox/%3C029B8F80-6C99-41C0-B47C-A334667E25BA@apache.org%3E|release notes]=
] to the [[http://mail-archives.apache.org/mod_mbox/www-announce/|announce]=
], [[http://mail-archives.apache.org/mod_mbox/couchdb-user/|couchdb-user]],=
 and [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/|couchdb-dev]] =
mailing lists.
  =

- 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 `downloads.html` listed a release that was not available on a local mir=
ror, or that was missing a corresponding tag in the Git repository. The cha=
nges should always propagate from the source, to the `dist` directory, to t=
he mirrors, to `downloads.html`, and finally to the actual release announce=
ment.
+ 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 Doing Housekeeping =3D
 =20