Dear Wiki user,

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

The "Test_procedure" page has been changed by NoahSlater:
http://wiki.apache.org/couchdb/Test_procedure?action=diff&rev1=36&rev2=37

- == Testing a Source Release ==
+ = Testing a Source Release =
  
  Any Apache CouchDB user is free to test a source release, and in fact we 
encourage you to do so!
  
@@ -8, +8 @@

  
  <<TableOfContents(2)>>
  
- === Setting Up ===
+ == Setting Up ==
  
  Remove any existing temporary directory:
  
@@ -28, +28 @@

  
  You can safely remove this directory and all of its contents when you're done.
  
- === Downloading the Release Candidate ===
+ == Downloading the Release Candidate ==
  
  You should have a copy of the vote email with links to the candidate files.
  
@@ -60, +60 @@

  
  If you don't have `wget` installed, you can use `curl -O` which should do the 
same thing.
  
- = Verifying the Candidate =
+ == Verifying the Candidate ==
  
  All release managers should have their keys in this file:
  
@@ -105, +105 @@

  
  Check for an "OK" message.
  
- = Checking the Candidate =
+ == Checking the Candidate ==
  
  ''Skip this section if you don't know anything about the build system.''
  
@@ -193, +193 @@

  
  This part of the process is left to your discretion.
  
- === Checking the Release Artefacts ===
+ == Checking the Release Artefacts ==
  
  Change into your `dist` directory:
  
@@ -306, +306 @@

  
  Your browser will lock up while the tests are run.
  
- === Wrapping it Up ===
+ == Wrapping it Up ==
  
  If you manage to get all the way through this without a single error, the 
release is good. Please reply to the vote email with a summary of the steps you 
completed. If anything strange happens, or you run into any problems, please 
reply to the vote email with an outline of the steps you took, and the problems 
you noticed. In some cases, it might be due to a slight difference in test 
setup. If that is the case, please update this document to help future testers.
  

Reply via email to