Dear wiki user, You have subscribed to a wiki page "Couchdb Wiki" for change notification.
The page "Windows_Binary_Packages" has been deleted by JoanTouzet: https://wiki.apache.org/couchdb/Windows_Binary_Packages?action=diff&rev1=97&rev2=98 Comment: Obsolete info - links are dead, process is wrong - moved to new cwiki - ## page was renamed from Windows_Binary_Releases - ## page was renamed from Windows Binary Releases - ## page was renamed from Binary_Releases - ## 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 package, but they are usually made by the committers. There is an important distinction between regular packages and snapshot packages, namely: - - * Packages to be distributed via the official Apache mirrors must be built from an official source release or signed tag equivalent - - * Snapshots may be provided at any time, from any tree-ish, but should be restricted to personal Apache space or elsewhere - - 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]], branched and 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 [[https://dist.apache.org/repos/dist/dev/couchdb/binary/win|the svn repository]] under {{{/$RELEASE/$VERSION}}}. - - Send an email to the [[mailto:d...@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]]. - * Validate the MD5 and SHA digests using [[http://md5deep.sourceforge.net/|md5 and sha for Windows]] or similar - * Run the installer directly, into a separate directory, or use the [[http://innounp.sourceforge.net/|Inno setup unpacker]]. There is no requirement to uninstall your existing CouchDB. - * Confirm using antivirus software there are no viruses or malware present. Microsoft provides the free [[http://windows.microsoft.com/en-GB/windows/products/security-essentials|Security Essentials]]. - * Start CouchDB via the provided {{{couchdb.bat}}} script. - * Use Futon to run the basic [[http://127.0.0.1:5984/_utils/verify_install.html|user verification]] tests. There is no need to run the full [[http://127.0.0.1:5984/_utils/couch_tests.html?script/couch_tests.js|dev test suite]], as these are being removed in coming releases anyway, for a more robust command-line test suite during build time. - - * 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 = - - * Reply to the original binary package proposal - for example; - {{{ - +1 - Windows 7 x64 SP1 - Firefox 10.12 - gpg sig OK - md5 & sha OK - No malware detected - End-user verification OK - }}} - - * If the original source artefact vote is aborted, please ensure you remove any copies of the binary to avoid these escaping into the wild. - * Full details are on the main CouchDB [[Release_procedure|Release procedure]]. - - After the source artefact vote is successful, three things must be updated: - - * Approved binaries and sha/md5/asc keys to be moved into the official Apache CouchDB {{{/www/www.apache.org/dist/couchdb/binary/win32/x.y.z/}}} environment - * Subsequent update of CouchDB downloads page. - * Once these are available on mirrors, the confirmation announcement can be sent. - - = NOTES = - * 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, let us know on the [[http://mail-archives.apache.org/mod_mbox/couchdb-dev/|couchdb-dev]] mailing list. -
