couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <>
Subject Re: [PROPOSAL] New release procedure
Date Fri, 08 Mar 2013 01:53:35 GMT
It means that the only testing that I will do before calling a vote on the
candidate will be basic build system tests. Once the candidate is published
and vote has started, I will download the candidate and test it properly
along with everyone else.

Please remember that I will be calling a discussion thread before we get to
this stage. We should not get to a vote if the test suite is failing,
because people should be checking this, or Travis should be failing.

On 8 March 2013 01:50, Wendall Cada <> wrote:

> On 03/07/2013 05:42 PM, Noah Slater wrote:
>> Hello devs,
>> I would like to propose a new release procedure:
>> This proposal will pass on lazy consensus, so speak up if you want to
>> object.
>> How this differs from the old release procedure:
>> 1) Code level tests (CLI, etap, etc) have been removed. The test procedure
>> has been updated to include an additional "make distcheck" step. This will
>> allow release candidates to go up very quickly, and puts the onus on you
>> guys to test things thoroughly.
> Does this mean testing will just be done by people voting on the release
> candidates? I don't have any objection, this is very reasonable, just
> curious.
> Wendall
>  2) The hashing and signing step has been split out from the build. This
>> allows the build to take place on a remote host that is not trusted with
>> your GPG key. I have also added an explicit step for checking
>> the authenticity of the tarball that is produced.
>> 3) As much as possible has been automated. The scripts are a bit rough and
>> ready, but they will do, provided you follow the instructions precisely.
>> Once again, the hope is that this will make releasing less burdensome for
>> the release manager.
>> Please take the time to review the document, and to review the scripts.
>> The scripts are in the couchdb-admin.git repository:
>> Please take the time to review these also.
>> The release procedure, and indeed the scripts, are not finished. They
>> never
>> will be. I will be updating them over the next day or two, and during the
>> 1.3.0 release. But they are finished enough that I am comfortable making
>> this proposal to the list.
>> Also, sorry for the noise. Testing against Subversion is... Tricky. :)
>> Thanks,


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message