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_Packages" by NoahSlater
Date Tue, 03 Apr 2012 21:28:46 GMT
Dear Wiki user,

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

The "Windows_Binary_Packages" page has been changed by NoahSlater:
http://wiki.apache.org/couchdb/Windows_Binary_Packages?action=diff&rev1=91&rev2=92

  ## page was copied from Release_procedure
  <<Include(EditTheWiki)>>
  
- This page details how Windows binaries are validated and voted on. Any Apache CouchDB committer
is free to make a binary snapshot or release, but they are usually made by the release team.
There is an important distinction between snapshots and releases, namely:
+ This page details how Windows binaries are validated and voted on. Any Apache CouchDB committer
is free to make a binary package, but they are usually made by the committers. There is an
important distinction between regular packages and snapshot packages, namely:
  
+  * Regular packages must be built from an official source release
-  * Snapshots may be provided at any time, and have no significance or expectations attached
to them
-  * Releases must be cut from the same source tag or commit sha used for a preceding Source
Release
  
- This distinction ensures that the user community can rely on the same functionality cross-platform
for Releases, and that the developer community is not obligated to maintain or support snapshots.
+  * Snapshots may be provided at any time, and may be built directly from the source
+ 
+ Regular packages may be linked to from the CouchDB website, and promoted alongside the source
releases. Snapshot packages are for developers only, and will not be promoted. This distinction
ensures that the user community can rely on binary packages corresponding to source releases,
and that the developer community can test binary packages while not being obligated to maintain
or support them.
  
  <<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]],
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]].
  
- 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]].
+ Send an email to the [[mailto:dev@couchdb.apache.org|dev@ mailing list]], requesting feedback
on the proposed 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.
  
   * [[http://www.apache.org/info/verification.html|Verify]] the GPG [[http://www.apache.org/dev/release-signing.html#verifying-signature|signature]].
Additional tips are available at [[http://gpg4win.de/handbuecher/novices.html|Introduction
to GPG for Windows]].
@@ -38, +41 @@

  
  == Giving Feedback on the Binaries ==
  
-  * Reply to the original Binary Release announcement - for example;
+  * Reply to the original binary package proposal - for example;
   {{{
  +1
  Windows 7 x64 SP1

Mime
View raw message