Actually...we have *multiple* CI pipelines that run on every check-in across 
multiple versions of Erlang and multiple operating systems: 


Travis CI: https://travis-ci.org/apache/couchdb 
Jenkins CI: 
https://builds.apache.org/blue/organizations/jenkins/CouchDB/branches/ 


Those CI pipelines also have status badges on our main GitHub repo: 
https://github.com/apache/couchdb 


So yes, we are doing lots of automated testing, and it is a Very Good Thing for 
our project. :D 




However, the Apache Software Foundation *official* release policy is more 
involved and *mandates* human involvement in the form of a vote: 


https://apache.org/legal/release-policy.html#approving-a-release 


Here are CouchDB's specific policies and procedures on releases, which outline 
the specific kinds of testing we require from our committers before voting on a 
release candidate: 


http://couchdb.apache.org/bylaws.html 
https://cwiki.apache.org/confluence/display/COUCHDB/Release+Procedure 


Best, 
Joan 

----- Original Message -----

From: "Geoffrey Cox" <redge...@gmail.com> 
To: dev@couchdb.apache.org, "Joan Touzet" <woh...@apache.org> 
Sent: Saturday, 4 November, 2017 3:39:43 PM 
Subject: Re: [VOTE] Release Apache CouchDB 2.1.1-RC2 


Quick question: it looks like everyone is testing the release manually. Have 
you all considered setting up something like a CI env that uses vagrant to spin 
up different VMs and test everything in an automated fashion? Sorry, if I am 
oversimplifying this :) 


On Sat, Nov 4, 2017 at 10:33 AM Joan Touzet < woh...@apache.org > wrote: 


+1-ing my own nomination: 

Tested on Debian jessie, x86_64 - Erlang/JS test suites and Fauxton smoke tests 
pass. 

Will check Windows later today. 

-Joan 

----- Original Message ----- 
From: "Joan Touzet" < woh...@apache.org > 
To: "CouchDB Developers" < dev@couchdb.apache.org > 
Sent: Wednesday, 1 November, 2017 6:21:32 PM 
Subject: [VOTE] Release Apache CouchDB 2.1.1-RC2 

Dear community, 

I would like to release Apache CouchDB 2.1.1-RC2. 

Changes since 2.1.1-RC1 are here: 

https://github.com/apache/couchdb/compare/2.1.1-RC1...2.1.1-RC2 

Human-readable change notes are here: 

http://docs.couchdb.org/en/latest/whatsnew/2.1.html#version-2-1-1 

We encourage the whole community to download and test these release artefacts 
so that any critical issues can be resolved before the release is made. 
Everyone is free to vote on this release, so dig right in! 

The release artefacts we are voting on are available here: 

wget 
https://dist.apache.org/repos/dist/dev/couchdb/source/2.1.1/rc.2/apache-couchdb-2.1.1-RC2.tar.gz
 
wget 
https://dist.apache.org/repos/dist/dev/couchdb/source/2.1.1/rc.2/apache-couchdb-2.1.1-RC2.tar.gz.asc
 
wget 
https://dist.apache.org/repos/dist/dev/couchdb/source/2.1.1/rc.2/apache-couchdb-2.1.1-RC2.tar.gz.sha256
 
wget 
https://dist.apache.org/repos/dist/dev/couchdb/source/2.1.1/rc.2/apache-couchdb-2.1.1-RC2.tar.gz.sha512
 

Please follow the test procedure here: 

https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release 

Please remember that "rc.2" is an annotation. If the vote passes, these 
artefacts will be released as Apache CouchDB 2.1.1. 

Please cast your votes now. 

Thanks, 
Joan Touzet 



Reply via email to