couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Couchdb Wiki] Update of "Release_Procedure" by NoahSlater
Date Sun, 10 Mar 2013 19:56: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:
http://wiki.apache.org/couchdb/Release_Procedure?action=diff&rev1=162&rev2=163

  
  <<TableOfContents(2)>>
  
- = Admin Resources =
+ == Admin Resources ==
  
  Grab a copy of the admin resources:
  
@@ -33, +33 @@

  
  ''You are responsible for the actions these scripts take.''
  
- = Preparing the Docs =
+ == Preparing the Docs ==
  
  Run through the following items by hand:
  
@@ -150, +150 @@

  
  This will be significantly faster than running the script from scratch again.
  
- = Preparing the Community =
+ == Preparing the Community ==
  
  ''This section will eventually include a step that requires you to check Travis.''
  
@@ -184, +184 @@

  
  Copy the text from that file and send an email to the `dev@couchdb.apache.org` mailing list.
  
- = Preparing the Candidate =
+ == Preparing the Candidate ==
  
  If the proposal meets no objection, you can continue.
  
@@ -217, +217 @@

  
  The `ish` file contains the tree-ish of the branch the release was taken from.
  
- = Using a Build Host =
+ == Using a Build Host ==
  
  You may use a build host to prepare the release candidate.
  
@@ -229, +229 @@

  
  All other parts of this process must be done on your local machine. 
  
- = Checking the Candidate =
+ == Checking the Candidate ==
  
  Assume that you cannot trust:
  
@@ -248, +248 @@

  
  This part of the process is left to your discretion.
  
- = Release Signing =
+ == Release Signing ==
  
  You will need a GPG key pair to sign the release.
  
@@ -276, +276 @@

  gpg --list-keys
  }}}
  
- = Publishing the Candidate =
+ == Publishing the Candidate ==
  
  Once you are satisfied with the release candidate, you can sign it, publish it, and call
a vote.
  
@@ -322, +322 @@

  
  The vote is now underway.
  
- = Preparing the Binary packages =
+ == Preparing the Binary packages ==
  
  At this point in the process, you should reach out to the following people:
  
@@ -333, +333 @@

  
  If these are done in time, they can be mentioned in the release announcement.
  
- = Preparing the Release Notes =
+ == Preparing the Release Notes ==
  
  ''Please note that this section of the release procedure is going to be replaced soon.''
  
@@ -389, +389 @@

  
  Add these files, and commit them back to Subversion.
  
- = Wrapping Up the Vote =
+ == Wrapping Up the Vote ==
  
  You need to wait a minimum of 72 hours.
  
@@ -415, +415 @@

  
  (You should replace values as necessary.)
  
- = Making the Release =
+ == Making the Release ==
  
  It is good to send release announcements on a Tuesday, for maximum impact.
  
@@ -460, +460 @@

  
  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
present.
@@ -475, +475 @@

   * Call a discussion on the dev@couchdb.apache.org mailing list about archiving old releases.
     * To archive an old release, remove it from [[http://wiki.apache.org/couchdb/CurrentReleases|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`
directory.
  
- = Troubleshooting =
+ == Troubleshooting ==
  
  If you get an error about not being able to find `pdflatex` and you're running on OS X,
first make sure that you have MacTeX installed. If you do, and you're still experiencing an
error, it might be the case that MacTeX has failed to set up your `PATH` properly.
  
@@ -487, +487 @@

  
  Obviously, replace the arguments to `build_candidate.sh` as appropriate.
  
- = Useful Resources =
+ == Useful Resources ==
  
   * http://www.apache.org/dev/release.html
   * http://incubator.apache.org/guides/releasemanagement.html#best-practice

Mime
View raw message