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 "Windows_Binary_Releases" by DaveCottlehuber
Date Fri, 30 Mar 2012 17:23:25 GMT
Dear Wiki user,

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

The "Windows_Binary_Releases" page has been changed by DaveCottlehuber:
http://wiki.apache.org/couchdb/Windows_Binary_Releases?action=diff&rev1=89&rev2=90

Comment:
comply with ASF policies on source releases vs binaries

  <<TableOfContents(2)>>
  
  = Introduction =
- Following an official source vote, a Windows binary is created. The procedure for this is
documented in [[https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=blob;f=INSTALL.Windows;hb=HEAD|INSTALL.Windows]]
and a scripted approach is available in the appropriate branch of [[https://github.com/dch/glazier/|glazier]].
+ Following an official source vote, a Windows binary is created. The procedure for this is
documented in [[https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=blob;f=INSTALL.Windows;hb=HEAD|INSTALL.Windows]]
and a scripted approach is available in the appropriate branch of [[https://github.com/dch/glazier/|glazier]],
tagged per source release.
  
  After the binary is built, it is then [[http://www.apache.org/dev/release-signing.html#sign-release|signed]]
and uploaded to the appropriate committer's [[https://people.apache.org/~id|apache site]].
  
- The release manager will send a notice to the [[mailto:user@couchdb.apache.org|user@ mailing
list]], requesting a vote on the new artefact. This follows the general [[Release_procedure|CouchDB
release procedure]].
+ Send a notice to the [[mailto:dev@couchdb.apache.org|dev@ mailing list]], requesting feedback
on the new binaries. This should follow the general [[Release_procedure|CouchDB release procedure]]
for consistency. Ensure you link to the [[#Testing|test procedure]].
  
  = Testing =
  Overall we are interested that the binary is malware free, correctly signed, and digests
match, and functionality matches that of the original source tarball.
@@ -35, +35 @@

  
   * FIX LATER: Double-check `README`, `INSTALL.Windows`, `NEWS`, `LICENSE`, and `CHANGES`
files are present in {{{%COUCHDIR%/share/doc/couchdb/}}} and contents is appropriate. At present
these are gzipped but this should be fixed, and added as shortcuts.
  
+ == Giving Feedback on the Binaries ==
- = Voting and Voters =
-  * [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/200907.mbox/<20090716211304.GA17172@tumbolia.org>|Call
a vote]] on the [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/|couchdb-dev]] mailing
list.
-  * Ensure you link to the [[#Testing|test procedure]].
- 
- If you are voting:
  
   * Reply to the original Binary Release announcement - for example;
   {{{
@@ -53, +49 @@

  Futon tests failed
  [... tedious details ommitted.. ]
  }}}
-  * If the vote is aborted, please ensure you remove any copies of the binary to avoid these
escaping into the wild
+  * If the original source artefact vote is aborted, please ensure you remove any copies
of the binary to avoid these escaping into the wild.
- 
- If you are tallying:
- 
-  * After 72 hours have elapsed without any -1 votes, and with at least 3 +1 votes, send
a confirmation.
-  * If aborted, ensure a summary is sent out with any follow-up actions required, and by
whom.
   * Full details are on the main CouchDB [[Release_procedure|Release procedure]].
  
+ After the source artefact vote is successful, three things must be updated:
- = Release =
- On an unsuccessful vote, ensure that the invalidated artefacts are removed from apache infrastructure,
to avoid these escaping into the wild.
- 
- For a successful vote, three things must be updated:
  
   * Approved binaries with sha/md5/asc keys to be moved into the official Apache CouchDB
{{{dist}}} environment.
   * Subsequent update of CouchDB downloads page.
@@ -74, +62 @@

   * currently working with HTTPD team to see if the new fancypants code signing is usable
   * still need way of referencing the detailed build process, and labelling artefacts.
  
- If you'd like to help out with making a release, lets us know on the [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/|couchdb-dev]]
mailing list.
+ If you'd like to help out, let us know on the [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/|couchdb-dev]]
mailing list.
  

Mime
View raw message