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 Thu, 05 Apr 2012 22:29:46 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:

  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 =
+ Go through the `NEWS` file and expand each bullet point as appropriate.
+ Format this document as HTML, and call it something like:
+ {{{
+ apache-couchdb-Y.Y.Y.html
+ }}}
+ Check that this HTML looks good when used for a draft blog post.
+ Then generate a text only version by running:
+ {{{
+ elinks -dump -no-numbering -no-references apache-couchdb-Y.Y.Y.html > apache-couchdb-Y.Y.Y.txt
+ }}}
+ Check the text only version to make sure that any important links are not lost.
+ For example, a JIRA ticket that is not referenced by number.
+ Upload these files to `/www/` on ``.

  = Making the Release =
  Create a signed tag:
@@ -242, +266 @@

   * Copy the release directory to `/www/` on ``.
     * Make sure that the release directory and all the files within it are owned by the `couchdb`
group and are group writable.
   * Wait for all changes to be synced to public mirrors.
-  * Update
+  * Update to point to the new files.
   * Send a pre-announcement email to [[|couchdb-dev]]
mailing list, so that downstream distributors can prepare their own announcements.
   * Wait for all changes to be synced to the public site.
+  * Publish a blog post using the HTML version of the release notes.
-  * Make a [[|release
announcement]] to the [[|announce]],
[[|couchdb-user]], and [[|couchdb-dev]]
mailing lists.
+  * Send the [[|release
notes]] to the [[|announce]], [[|couchdb-user]],
and [[|couchdb-dev]] mailing lists.
  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 `downloads.html` 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.

View raw message