couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Couchdb Wiki] Update of "Release_procedure" by NoahSlater
Date Mon, 07 May 2012 22:05:31 GMT
Dear Wiki user,

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

The "Release_procedure" page has been changed by NoahSlater:

+ = Release Procedure =
- = Making a Source Release =
+ == Making a Source Release ==
  Any Apache CouchDB committer is free to make a source release, but they are usually made
by the release team.
@@ -10, +12 @@

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

       * 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.
- = Preparing the Community =
+ == Preparing the Community ==
  Call a vote on the [[|couchdb-dev]]
mailing list asking for a request for comments on the release. Ask all developers to specifically
check the `NEWS` and `CHANGES` file for anything that has been added in this release.
- = Preparing the Release =
+ == Preparing the Release ==
  First make sure your local repository has everything from the public repository:
@@ -84, +86 @@

  cd Y.Y.Y
- = Release Signing =
+ == Release Signing ==
  You will need a GPG key pair to sign the release.
@@ -112, +114 @@

  gpg --list-keys
- = Creating the Release Artefacts =
+ == Creating the Release Artefacts ==
  To build the source for distribution you should then run the following command:
@@ -127, +129 @@

   * apache-couchdb-Y.Y.Y.tar.gz.md5
   * apache-couchdb-Y.Y.Y.tar.gz.sha
- = Checking the Release Contents =
+ == Checking the Release Contents ==
  Remove any existing temporary directory:
@@ -189, +191 @@

  Do not upload the exported tag directory, of course. That was only for testing.
- = Calling a Vote =
+ == Calling a Vote ==
  Before you call the vote, you should now download your own release artefacts and run the
[[Test_procedure|test procedure]] with them.
@@ -209, +211 @@

  A vote can only pass if there are at least three +1 votes. These votes can come from anyone,
including non-committers, and in fact, everyone is encouraged to partake in and vote on each
release. However, it is preferable that 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 anyone votes -1 or expresses any serious concern, that should be addressed. Usually, this
will be cause to abort the vote. A vote can only be closed after three working days. This
allows most people a chance to test and vote on the release.
- = Preparing the Release Notes =
+ == Preparing the Release Notes ==
  Go through the `NEWS` file and expand each bullet point as appropriate.
@@ -233, +235 @@

  Upload these files to `/www/` on ``.

- = Making the Release =
+ == Making the Release ==
  Create a signed tag:
@@ -275, +277 @@

  At each stage of the actual release, it is expected that a person can follow 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 mirrors, to `downloads.html`,
and finally to the actual release announcement.
- = Doing Housekeeping =
+ == Doing Housekeeping ==
   * Add a new release section to `NEWS` and `CHANGES` on master if not already present.
   * Add a new release section to `NEWS` and `CHANGES` on Y.Y.x the branch if not already
@@ -290, +292 @@

   * Call a discussion on the [[|couchdb-dev]]
mailing list about archiving old releases.
     * To archive an old release, remove it from [[|the
wiki]] and then delete the corresponding directory from the `dist` directory. Do not worry
about the release artefacts no longer being available, they are automatically mirrored to
the Apache archive site and will remain there even after they are deleted from the main `dist`
- = Useful Resources =
+ == Useful Resources ==

View raw message