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 Tue, 25 Jun 2013 20:33:52 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:
https://wiki.apache.org/couchdb/Release_Procedure?action=diff&rev1=223&rev2=224

  git clone http://git-wip-us.apache.org/repos/asf/couchdb-admin.git
  }}}
  
+ Any path in this document that references the "couchdb-admin" directory should be modified
to point to this Git clone. 
- Change in to the admin resources directory:
- 
- {{{
- cd couchdb-admin
- }}}
- 
- The commands in this document assume this as a working directory.
  
  Some of these scripts take actions on your behalf, such accessing `people.apache.org` or
checking files into Subversion.
  
@@ -61, +55 @@

  The notice email can be found here:
  
  {{{
- email/notice_release.txt
+ couchdb-admin/email/notice_release.txt
  }}}
  
  The merge request email can be found here:
  
  {{{
- email/request_merge.txt
+ couchdb-admin/email/request_merge.txt
  }}}
  
  The VOTE and DISCUSS threads are covered by the rest of these instructions.
@@ -92, +86 @@

  Build a list of CVE numbers:
  
  {{{
- ./release/build_cve_list.sh 
+ ./couchdb-admin/release/build_cve_list.sh 
  }}}
  
  This will produce output that ends with something like this:
@@ -105, +99 @@

  Check the documentation:
  
  {{{
- ./release/check_docs.sh CVE_LIST_FILE
+ ./couchdb-admin/release/check_docs.sh CVE_LIST_FILE
  }}}
  
  Replace ''CVE_LIST_FILE'' with the file generated by the `build_cve_list.sh` script.
@@ -113, +107 @@

  So, in this instance, you would run:
  
  {{{
- ./release/check_docs.sh /tmp/build_cve_list.sh.9PhpoO/cve_list.txt
+ ./couchdb-admin/release/check_docs.sh /tmp/build_cve_list.sh.9PhpoO/cve_list.txt
  }}}
  
  This is going to check several things for you.
@@ -174, +168 @@

  You can copy that directory name and append it the command to re-use the cached data:
  
  {{{
- ./release/check_docs.sh CVE_LIST_FILE CACHE_DIR
+ ./couchdb-admin/release/check_docs.sh CVE_LIST_FILE CACHE_DIR
  }}}
  
  Replace ''CVE_LIST_FILE'' with the file generated by the `build_cve_list.sh` script.
@@ -184, +178 @@

  So, in this instance, you would run:
  
  {{{
- ./release/check_docs.sh /tmp/build_cve_list.sh.9PhpoO/cve_list.txt /tmp/check_docs.sh.9oNHt9
+ ./couchdb-admin/release/check_docs.sh /tmp/build_cve_list.sh.9PhpoO/cve_list.txt /tmp/check_docs.sh.9oNHt9
  }}}
  
  This will be significantly faster than running the script from scratch again.
@@ -200, +194 @@

  Generate a release proposal:
  
  {{{
- ./email/discuss_release.sh CACHE_DIR BRANCH VERSION
+ ./couchdb-admin/email/discuss_release.sh CACHE_DIR BRANCH VERSION
  }}}
  
  Replace `CACHE_DIR` with the temporary directory name from the `check_docs.sh` script.
@@ -212, +206 @@

  So, in this instance, you might run:
  
  {{{
- ./email/discuss_release.sh /tmp/check_docs.sh.9oNHt9 1.3.x 1.3.0
+ ./couchdb-admin/email/discuss_release.sh /tmp/check_docs.sh.9oNHt9 1.3.x 1.3.0
  }}}
  
  This will output something like:
@@ -232, +226 @@

  Build a release candidate:
  
  {{{
- ./release/build_candidate.sh BRANCH VERSION
+ ./couchdb-admin/release/build_candidate.sh BRANCH VERSION
  }}}
  
  Replace `BRANCH` with the branch you are releasing from.
@@ -242, +236 @@

  So, in this instance, you might run:
  
  {{{
- ./release/build_candidate.sh 1.3.x 1.3.0
+ ./couchdb-admin/release/build_candidate.sh 1.3.x 1.3.0
  }}}
  
  This will do everything that is required to prepare the release candidate for you.
@@ -328, +322 @@

  You can do all of these things at once by running:
  
  {{{
- ./release/publish_candidate.sh CACHE_DIR BRANCH VERSION CANDIDATE
+ ./couchdb-admin/release/publish_candidate.sh CACHE_DIR BRANCH VERSION CANDIDATE
  }}}
  
  Replace `CACHE_DIR` with the output from the `build_candidate.sh` script.
@@ -340, +334 @@

  So, in this instance, you might run:
  
  {{{
- ./release/publish_candidate.sh /tmp/build_candidate.sh.DOtlGR 1.3.x 1.3.0 1
+ ./couchdb-admin/release/publish_candidate.sh /tmp/build_candidate.sh.DOtlGR 1.3.x 1.3.0
1
  }}}
  
  The candidate number should start at 1 and increase with each successive vote.
@@ -348, +342 @@

  If the vote fails, and you're doing a second, you might run:
  
  {{{
- ./release/publish_candidate.sh /tmp/build_candidate.sh.DOtlGR 1.3.x 1.3.0 2
+ ./couchdb-admin/release/publish_candidate.sh /tmp/build_candidate.sh.DOtlGR 1.3.x 1.3.0
2
  }}}
  
  If you attempt to publish a duplicate candidate number, you will get a cryptic Subversion
error.
@@ -374, +368 @@

  After you've done that, open this file:
  
  {{{
- email/request_binaries.txt
+ couchdb-admin/email/request_binaries.txt
  }}}
  
  Copy the text from that file and send an email to the `dev@couchdb.apache.org` mailing list.
@@ -469, +463 @@

  
  Replace `CANDIDATE` with the candidate number.
  
- Copy the template file from the admin resources directory:
+ Copy the template file:
  
  {{{ 
- cp ./notes/template.html /tmp/couchdb/notes/apache-couchdb-VERSION.html
+ cp ./couchdb-admin/notes/template.html /tmp/couchdb/notes/apache-couchdb-VERSION.html
  }}}
  
  Replace `VERSION` with the version you are releasing.
@@ -514, +508 @@

  Open this file:
  
  {{{
- email/request_notes.txt
+ couchdb-admin/email/request_notes.txt
  }}}
  
  Copy the text from that file and send an email to the `dev@couchdb.apache.org` mailing list.
@@ -587, +581 @@

  When the vote passes, open this file:
  
  {{{
- email/result_release.txt
+ couchdb-admin/email/result_release.txt
  }}}
  
  Copy the text from that file and send an email to the `dev@couchdb.apache.org` mailing list.
@@ -600, +594 @@

  
  You may choose to time the rest of these steps to line up with a Tuesday release announcement
date.
  
- Change in to the admin resources directory:
- 
- {{{
- cd couchdb-admin
- }}}
- 
  Tag the candidate:
  
  {{{
- ./release/tag_candidate.sh VERSION CANDIDATE GPG_KEY
+ ./couchdb-admin/release/tag_candidate.sh VERSION CANDIDATE GPG_KEY
  }}}
  
  Replace `VERSION` with the version you are releasing.
@@ -646, +634 @@

  
  Choose a date for the release. Tuesdays mornings PST are better, because they get more press
coverage.
  
+ 
  Open this file:
  
  {{{
- email/schedule_release.txt
+ couchdb-admin/email/schedule_release.txt
  }}}
  
  Copy the text from that file and send an email to the `dev@couchdb.apache.org` mailing list.
@@ -781, +770 @@

  Open this file:
  
  {{{
- email/request_promotion.txt
+ couchdb-admin/email/request_promotion.txt
  }}}
  
  Copy the text from that file into an email.
@@ -815, +804 @@

  Open this file:
  
  {{{
- email/schedule_release.txt
+ couchdb-admin/email/schedule_release.txt
  }}}
  
  Copy the text from that file and send an email to the `dev@couchdb.apache.org` mailing list.

Mime
View raw message