You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Joan Touzet <wo...@apache.org> on 2020/09/11 22:53:50 UTC
[VOTE] Release Apache CouchDB 3.1.1 (RC2)
Dear community,
I would like to propose that we release Apache CouchDB 3.1.1.
Changes since the last round:
https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
Candidate release notes:
https://docs.couchdb.org/en/latest/whatsnew/3.1.html
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!
(Only PMC members have binding votes, but they depend on community
feedback to gauge if an official release is ready to be made.)
The release artefacts we are voting on are available here:
https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
There, you will find a tarball, a GPG signature, and SHA256/SHA512
checksums.
Please follow the test procedure here:
https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
Please remember that "RC2" is an annotation. If the vote passes, these
artefacts will be released as Apache CouchDB 3.1.1.
Because of the weekend, this vote will remain open until 5PM ET (UTC-4),
Tuesday, 15 September 2020.
Please cast your votes now.
Thanks,
Joan "once more unto the breech, dear friends" Touzet
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Joan Touzet <wo...@apache.org>.
Tested on Windows 10 1909, Erlang 20.3.8.26, SM60
Cannot check my own signatures, but checksums match.
make check: some persistent test failures:
Issues filed: https://github.com/apache/couchdb/issues/3158
https://github.com/apache/couchdb/issues/3159
I am not going to block this release on these tests as I
suspect these are harness-specific failures; however, if it is
found post-release that JWT or ProxyAuth fail on Windows, we
can spin a new release at that time. Neither is functionality
that will break existing users.
+1
-Joan
On 17/09/2020 10:58, Jan Lehnardt wrote:
> +1
>
> CouchDB Mojave 10.14.6, Erlang 22, SM60.
>
> Signatures: ok
> make check: ok
>
> Mac convenience binaries:
>
>
> https://dist.apache.org/repos/dist/dev/couchdb/binary/mac/3.1.1/rc.2/
>
> I could not reproduce the test errors on Mojave, and it’ll be some time before I can have a Catalina (10.15) build env, but I’ll look for a repro then.
>
> Best
> Jan
> —
>
>> On 12. Sep 2020, at 00:53, Joan Touzet <wo...@apache.org> wrote:
>>
>> Dear community,
>>
>> I would like to propose that we release Apache CouchDB 3.1.1.
>>
>> Changes since the last round:
>>
>> https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
>>
>> Candidate release notes:
>>
>> https://docs.couchdb.org/en/latest/whatsnew/3.1.html
>>
>> 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! (Only PMC members have binding votes, but they depend on community feedback to gauge if an official release is ready to be made.)
>>
>> The release artefacts we are voting on are available here:
>>
>> https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
>>
>> There, you will find a tarball, a GPG signature, and SHA256/SHA512 checksums.
>>
>> Please follow the test procedure here:
>>
>>
>> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
>>
>> Please remember that "RC2" is an annotation. If the vote passes, these artefacts will be released as Apache CouchDB 3.1.1.
>>
>> Because of the weekend, this vote will remain open until 5PM ET (UTC-4), Tuesday, 15 September 2020.
>>
>> Please cast your votes now.
>>
>> Thanks,
>> Joan "once more unto the breech, dear friends" Touzet
>
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Jan Lehnardt <ja...@apache.org>.
+1
CouchDB Mojave 10.14.6, Erlang 22, SM60.
Signatures: ok
make check: ok
Mac convenience binaries:
https://dist.apache.org/repos/dist/dev/couchdb/binary/mac/3.1.1/rc.2/
I could not reproduce the test errors on Mojave, and it’ll be some time before I can have a Catalina (10.15) build env, but I’ll look for a repro then.
Best
Jan
—
> On 12. Sep 2020, at 00:53, Joan Touzet <wo...@apache.org> wrote:
>
> Dear community,
>
> I would like to propose that we release Apache CouchDB 3.1.1.
>
> Changes since the last round:
>
> https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
>
> Candidate release notes:
>
> https://docs.couchdb.org/en/latest/whatsnew/3.1.html
>
> 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! (Only PMC members have binding votes, but they depend on community feedback to gauge if an official release is ready to be made.)
>
> The release artefacts we are voting on are available here:
>
> https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
>
> There, you will find a tarball, a GPG signature, and SHA256/SHA512 checksums.
>
> Please follow the test procedure here:
>
>
> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
>
> Please remember that "RC2" is an annotation. If the vote passes, these artefacts will be released as Apache CouchDB 3.1.1.
>
> Because of the weekend, this vote will remain open until 5PM ET (UTC-4), Tuesday, 15 September 2020.
>
> Please cast your votes now.
>
> Thanks,
> Joan "once more unto the breech, dear friends" Touzet
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Jan Lehnardt <ja...@apache.org>.
> On 14. Sep 2020, at 15:02, Robert Samuel Newson <rn...@apache.org> wrote:
>
> Hi,
>
> There is no existing HTTP request header that I'm aware of that could cover this and inventing custom HTTP headers is not recommended (CouchDB has a fair few but I don't want to add to that pile).
>
> My preference is to remove the query parameter without replacement for this release, leaving it as just an administrator setting. We can enhance this in a future release.
Why should we remove this? I don’t think it is controversial.
Best
Jan
—
>
> B.
>
>> On 14 Sep 2020, at 13:51, Jan Lehnardt <ja...@apache.org> wrote:
>>
>> On 14. Sep 2020, at 12:45, Richard Ellis <RI...@uk.ibm.com> wrote:
>>>
>>> I've got concerns about the proposed API for the new buffer_response
>>> option. I have no issues with the intended behaviour or the chttp config
>>> option, but the choice of using a URL query parameter to control it when
>>> using the option "per request" seems unusual to me.
>>>
>>> As per HTTP spec https://tools.ietf.org/html/rfc7231#section-5
>>>
>>> "A client sends request header fields to ... **or modify the expected
>>> request processing**."
>>>
>>> As per URL spec https://tools.ietf.org/html/rfc3986#section-3.4
>>>
>>> "The query component contains non-hierarchical data that, along with data
>>> in the path component (Section 3.3), **serves to identify a resource**
>>> within the scope of the URI's scheme"
>>>
>>> Since this is a directive controlling the request processing on the server
>>> and is unrelated to identifying the resources it seems to me that the
>>> proposal is counter-intuitive to the specs and the option would be better
>>> placed in a header than a URL query parameter. It's not clear to me if
>>> there is some technical reason why a query parameter is preferable here or
>>> if this is perhaps following some (unknown to me) API convention or
>>> existing Couch API precedent (the closest thing I could think of was the r
>>> & w quorum options).
>>>
>>> Could anyone explain the API design choice to me or does anyone else have
>>> any concerns about this?
>>
>> I think your reading of the HTTP spec is apt and I wouldn’t object to an
>> addition of a header to control the behaviour.
>>
>> In the past API designs we opted for pragmatic choices when it came to
>> qs vs. headers and you could make similar arguments about the ?feed=
>> qs for _changes and there are likely others, too, where we opted to use
>> qs over (or in addition to) headers because we wanted to make a certain
>> feature easily accessible to environments where passing headers is non-
>> trivial, mostly, that’s a browser’s URL bar.
>>
>> I happily concede that the use-case for this is rather minor, but especially
>> in debugging cases, this keeps coming in handy.
>>
>>
>>> On 14. Sep 2020, at 12:58, Bessenyei Balázs Donát <be...@apache.org> wrote:
>>>
>>> And I'm interested to see the discussion addressing Richard Ellis'
>>> concerns as any post-release changes to the "location" of the new
>>> control (qs -> header) would require a major version (in semver-land).
>>
>> I would say so, and in light of this, we wouldn’t like to a straight transition
>> but deprecating the qs until the next more naturally occurring major version
>> and then removing it later, sometimes even next+1 if we don’t want to make
>> the upgrade path unnecessarily hard for end-users.
>>
>>
>> Best
>> Jan
>> —
>>
>>>
>>
>>
>>> Thanks,
>>> Rich
>>>
>>>
>>>
>>> From: Joan Touzet <wo...@apache.org>
>>> To: CouchDB Developers <de...@couchdb.apache.org>
>>> Date: 11/09/2020 23:53
>>> Subject: [EXTERNAL] [VOTE] Release Apache CouchDB 3.1.1 (RC2)
>>>
>>>
>>>
>>> Dear community,
>>>
>>> I would like to propose that we release Apache CouchDB 3.1.1.
>>>
>>> Changes since the last round:
>>>
>>>
>>> https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
>>>
>>>
>>> Candidate release notes:
>>>
>>>
>>> https://docs.couchdb.org/en/latest/whatsnew/3.1.html
>>>
>>>
>>> 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!
>>> (Only PMC members have binding votes, but they depend on community
>>> feedback to gauge if an official release is ready to be made.)
>>>
>>> The release artefacts we are voting on are available here:
>>>
>>>
>>> https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
>>>
>>>
>>> There, you will find a tarball, a GPG signature, and SHA256/SHA512
>>> checksums.
>>>
>>> Please follow the test procedure here:
>>>
>>>
>>> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
>>>
>>>
>>> Please remember that "RC2" is an annotation. If the vote passes, these
>>> artefacts will be released as Apache CouchDB 3.1.1.
>>>
>>> Because of the weekend, this vote will remain open until 5PM ET (UTC-4),
>>> Tuesday, 15 September 2020.
>>>
>>> Please cast your votes now.
>>>
>>> Thanks,
>>> Joan "once more unto the breech, dear friends" Touzet
>>>
>>>
>>>
>>>
>>> Unless stated otherwise above:
>>> IBM United Kingdom Limited - Registered in England and Wales with number
>>> 741598.
>>> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Robert Samuel Newson <rn...@apache.org>.
Hi,
There is no existing HTTP request header that I'm aware of that could cover this and inventing custom HTTP headers is not recommended (CouchDB has a fair few but I don't want to add to that pile).
My preference is to remove the query parameter without replacement for this release, leaving it as just an administrator setting. We can enhance this in a future release.
B.
> On 14 Sep 2020, at 13:51, Jan Lehnardt <ja...@apache.org> wrote:
>
> On 14. Sep 2020, at 12:45, Richard Ellis <RI...@uk.ibm.com> wrote:
>>
>> I've got concerns about the proposed API for the new buffer_response
>> option. I have no issues with the intended behaviour or the chttp config
>> option, but the choice of using a URL query parameter to control it when
>> using the option "per request" seems unusual to me.
>>
>> As per HTTP spec https://tools.ietf.org/html/rfc7231#section-5
>>
>> "A client sends request header fields to ... **or modify the expected
>> request processing**."
>>
>> As per URL spec https://tools.ietf.org/html/rfc3986#section-3.4
>>
>> "The query component contains non-hierarchical data that, along with data
>> in the path component (Section 3.3), **serves to identify a resource**
>> within the scope of the URI's scheme"
>>
>> Since this is a directive controlling the request processing on the server
>> and is unrelated to identifying the resources it seems to me that the
>> proposal is counter-intuitive to the specs and the option would be better
>> placed in a header than a URL query parameter. It's not clear to me if
>> there is some technical reason why a query parameter is preferable here or
>> if this is perhaps following some (unknown to me) API convention or
>> existing Couch API precedent (the closest thing I could think of was the r
>> & w quorum options).
>>
>> Could anyone explain the API design choice to me or does anyone else have
>> any concerns about this?
>
> I think your reading of the HTTP spec is apt and I wouldn’t object to an
> addition of a header to control the behaviour.
>
> In the past API designs we opted for pragmatic choices when it came to
> qs vs. headers and you could make similar arguments about the ?feed=
> qs for _changes and there are likely others, too, where we opted to use
> qs over (or in addition to) headers because we wanted to make a certain
> feature easily accessible to environments where passing headers is non-
> trivial, mostly, that’s a browser’s URL bar.
>
> I happily concede that the use-case for this is rather minor, but especially
> in debugging cases, this keeps coming in handy.
>
>
>> On 14. Sep 2020, at 12:58, Bessenyei Balázs Donát <be...@apache.org> wrote:
>>
>> And I'm interested to see the discussion addressing Richard Ellis'
>> concerns as any post-release changes to the "location" of the new
>> control (qs -> header) would require a major version (in semver-land).
>
> I would say so, and in light of this, we wouldn’t like to a straight transition
> but deprecating the qs until the next more naturally occurring major version
> and then removing it later, sometimes even next+1 if we don’t want to make
> the upgrade path unnecessarily hard for end-users.
>
>
> Best
> Jan
> —
>
>>
>
>
>> Thanks,
>> Rich
>>
>>
>>
>> From: Joan Touzet <wo...@apache.org>
>> To: CouchDB Developers <de...@couchdb.apache.org>
>> Date: 11/09/2020 23:53
>> Subject: [EXTERNAL] [VOTE] Release Apache CouchDB 3.1.1 (RC2)
>>
>>
>>
>> Dear community,
>>
>> I would like to propose that we release Apache CouchDB 3.1.1.
>>
>> Changes since the last round:
>>
>>
>> https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
>>
>>
>> Candidate release notes:
>>
>>
>> https://docs.couchdb.org/en/latest/whatsnew/3.1.html
>>
>>
>> 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!
>> (Only PMC members have binding votes, but they depend on community
>> feedback to gauge if an official release is ready to be made.)
>>
>> The release artefacts we are voting on are available here:
>>
>>
>> https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
>>
>>
>> There, you will find a tarball, a GPG signature, and SHA256/SHA512
>> checksums.
>>
>> Please follow the test procedure here:
>>
>>
>> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
>>
>>
>> Please remember that "RC2" is an annotation. If the vote passes, these
>> artefacts will be released as Apache CouchDB 3.1.1.
>>
>> Because of the weekend, this vote will remain open until 5PM ET (UTC-4),
>> Tuesday, 15 September 2020.
>>
>> Please cast your votes now.
>>
>> Thanks,
>> Joan "once more unto the breech, dear friends" Touzet
>>
>>
>>
>>
>> Unless stated otherwise above:
>> IBM United Kingdom Limited - Registered in England and Wales with number
>> 741598.
>> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Jan Lehnardt <ja...@apache.org>.
On 14. Sep 2020, at 12:45, Richard Ellis <RI...@uk.ibm.com> wrote:
>
> I've got concerns about the proposed API for the new buffer_response
> option. I have no issues with the intended behaviour or the chttp config
> option, but the choice of using a URL query parameter to control it when
> using the option "per request" seems unusual to me.
>
> As per HTTP spec https://tools.ietf.org/html/rfc7231#section-5
>
> "A client sends request header fields to ... **or modify the expected
> request processing**."
>
> As per URL spec https://tools.ietf.org/html/rfc3986#section-3.4
>
> "The query component contains non-hierarchical data that, along with data
> in the path component (Section 3.3), **serves to identify a resource**
> within the scope of the URI's scheme"
>
> Since this is a directive controlling the request processing on the server
> and is unrelated to identifying the resources it seems to me that the
> proposal is counter-intuitive to the specs and the option would be better
> placed in a header than a URL query parameter. It's not clear to me if
> there is some technical reason why a query parameter is preferable here or
> if this is perhaps following some (unknown to me) API convention or
> existing Couch API precedent (the closest thing I could think of was the r
> & w quorum options).
>
> Could anyone explain the API design choice to me or does anyone else have
> any concerns about this?
I think your reading of the HTTP spec is apt and I wouldn’t object to an
addition of a header to control the behaviour.
In the past API designs we opted for pragmatic choices when it came to
qs vs. headers and you could make similar arguments about the ?feed=
qs for _changes and there are likely others, too, where we opted to use
qs over (or in addition to) headers because we wanted to make a certain
feature easily accessible to environments where passing headers is non-
trivial, mostly, that’s a browser’s URL bar.
I happily concede that the use-case for this is rather minor, but especially
in debugging cases, this keeps coming in handy.
> On 14. Sep 2020, at 12:58, Bessenyei Balázs Donát <be...@apache.org> wrote:
>
> And I'm interested to see the discussion addressing Richard Ellis'
> concerns as any post-release changes to the "location" of the new
> control (qs -> header) would require a major version (in semver-land).
I would say so, and in light of this, we wouldn’t like to a straight transition
but deprecating the qs until the next more naturally occurring major version
and then removing it later, sometimes even next+1 if we don’t want to make
the upgrade path unnecessarily hard for end-users.
Best
Jan
—
>
> Thanks,
> Rich
>
>
>
> From: Joan Touzet <wo...@apache.org>
> To: CouchDB Developers <de...@couchdb.apache.org>
> Date: 11/09/2020 23:53
> Subject: [EXTERNAL] [VOTE] Release Apache CouchDB 3.1.1 (RC2)
>
>
>
> Dear community,
>
> I would like to propose that we release Apache CouchDB 3.1.1.
>
> Changes since the last round:
>
>
> https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
>
>
> Candidate release notes:
>
>
> https://docs.couchdb.org/en/latest/whatsnew/3.1.html
>
>
> 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!
> (Only PMC members have binding votes, but they depend on community
> feedback to gauge if an official release is ready to be made.)
>
> The release artefacts we are voting on are available here:
>
>
> https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
>
>
> There, you will find a tarball, a GPG signature, and SHA256/SHA512
> checksums.
>
> Please follow the test procedure here:
>
>
> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
>
>
> Please remember that "RC2" is an annotation. If the vote passes, these
> artefacts will be released as Apache CouchDB 3.1.1.
>
> Because of the weekend, this vote will remain open until 5PM ET (UTC-4),
> Tuesday, 15 September 2020.
>
> Please cast your votes now.
>
> Thanks,
> Joan "once more unto the breech, dear friends" Touzet
>
>
>
>
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Richard Ellis <RI...@uk.ibm.com>.
I've got concerns about the proposed API for the new buffer_response
option. I have no issues with the intended behaviour or the chttp config
option, but the choice of using a URL query parameter to control it when
using the option "per request" seems unusual to me.
As per HTTP spec https://tools.ietf.org/html/rfc7231#section-5
"A client sends request header fields to ... **or modify the expected
request processing**."
As per URL spec https://tools.ietf.org/html/rfc3986#section-3.4
"The query component contains non-hierarchical data that, along with data
in the path component (Section 3.3), **serves to identify a resource**
within the scope of the URI's scheme"
Since this is a directive controlling the request processing on the server
and is unrelated to identifying the resources it seems to me that the
proposal is counter-intuitive to the specs and the option would be better
placed in a header than a URL query parameter. It's not clear to me if
there is some technical reason why a query parameter is preferable here or
if this is perhaps following some (unknown to me) API convention or
existing Couch API precedent (the closest thing I could think of was the r
& w quorum options).
Could anyone explain the API design choice to me or does anyone else have
any concerns about this?
Thanks,
Rich
From: Joan Touzet <wo...@apache.org>
To: CouchDB Developers <de...@couchdb.apache.org>
Date: 11/09/2020 23:53
Subject: [EXTERNAL] [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Dear community,
I would like to propose that we release Apache CouchDB 3.1.1.
Changes since the last round:
https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
Candidate release notes:
https://docs.couchdb.org/en/latest/whatsnew/3.1.html
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!
(Only PMC members have binding votes, but they depend on community
feedback to gauge if an official release is ready to be made.)
The release artefacts we are voting on are available here:
https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
There, you will find a tarball, a GPG signature, and SHA256/SHA512
checksums.
Please follow the test procedure here:
https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
Please remember that "RC2" is an annotation. If the vote passes, these
artefacts will be released as Apache CouchDB 3.1.1.
Because of the weekend, this vote will remain open until 5PM ET (UTC-4),
Tuesday, 15 September 2020.
Please cast your votes now.
Thanks,
Joan "once more unto the breech, dear friends" Touzet
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Joan Touzet <wo...@apache.org>.
Can anyone else repeat this failure or look at it? macOS only or others?
Don't see this on Linux.
I'm out for the rest of the day and if no one responds can look tomorrow.
Glynn you should be able to edit that wiki page, please do if you have
time :) thanks!
-Joan
On 14/09/2020 06:11, Glynn Bird wrote:
> macOS 10.15.6
> - checksums ok
> - build ok (had to use erlang@22 instead of default erlang @23 that brew
> gave me)
> - 3 tests failed repeatedly
>
> chttpd_view_test:75: should_succeed_on_view_with_queries_keys...*failed*
> chttpd_view_test:91:
> should_succeed_on_view_with_queries_limit_skip...*failed*
> chttpd_view_test:108:
> should_succeed_on_view_with_multiple_queries...*failed*
>
> I re-ran the tests in isolation and the same three failed again with:
>
> make check apps=chttpd suites=chttpd_view_test
>
> Note that the instructions on how to run individual tests is out-of-date in
> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
>
> On Fri, 11 Sep 2020 at 23:53, Joan Touzet <wo...@apache.org> wrote:
>
>> Dear community,
>>
>> I would like to propose that we release Apache CouchDB 3.1.1.
>>
>> Changes since the last round:
>>
>> https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
>>
>> Candidate release notes:
>>
>> https://docs.couchdb.org/en/latest/whatsnew/3.1.html
>>
>> 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!
>> (Only PMC members have binding votes, but they depend on community
>> feedback to gauge if an official release is ready to be made.)
>>
>> The release artefacts we are voting on are available here:
>>
>> https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
>>
>> There, you will find a tarball, a GPG signature, and SHA256/SHA512
>> checksums.
>>
>> Please follow the test procedure here:
>>
>>
>>
>> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
>>
>> Please remember that "RC2" is an annotation. If the vote passes, these
>> artefacts will be released as Apache CouchDB 3.1.1.
>>
>> Because of the weekend, this vote will remain open until 5PM ET (UTC-4),
>> Tuesday, 15 September 2020.
>>
>> Please cast your votes now.
>>
>> Thanks,
>> Joan "once more unto the breech, dear friends" Touzet
>>
>
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Glynn Bird <gl...@apache.org>.
macOS 10.15.6
- checksums ok
- build ok (had to use erlang@22 instead of default erlang @23 that brew
gave me)
- 3 tests failed repeatedly
chttpd_view_test:75: should_succeed_on_view_with_queries_keys...*failed*
chttpd_view_test:91:
should_succeed_on_view_with_queries_limit_skip...*failed*
chttpd_view_test:108:
should_succeed_on_view_with_multiple_queries...*failed*
I re-ran the tests in isolation and the same three failed again with:
make check apps=chttpd suites=chttpd_view_test
Note that the instructions on how to run individual tests is out-of-date in
https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
On Fri, 11 Sep 2020 at 23:53, Joan Touzet <wo...@apache.org> wrote:
> Dear community,
>
> I would like to propose that we release Apache CouchDB 3.1.1.
>
> Changes since the last round:
>
> https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
>
> Candidate release notes:
>
> https://docs.couchdb.org/en/latest/whatsnew/3.1.html
>
> 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!
> (Only PMC members have binding votes, but they depend on community
> feedback to gauge if an official release is ready to be made.)
>
> The release artefacts we are voting on are available here:
>
> https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
>
> There, you will find a tarball, a GPG signature, and SHA256/SHA512
> checksums.
>
> Please follow the test procedure here:
>
>
>
> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
>
> Please remember that "RC2" is an annotation. If the vote passes, these
> artefacts will be released as Apache CouchDB 3.1.1.
>
> Because of the weekend, this vote will remain open until 5PM ET (UTC-4),
> Tuesday, 15 September 2020.
>
> Please cast your votes now.
>
> Thanks,
> Joan "once more unto the breech, dear friends" Touzet
>
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Bessenyei Balázs Donát <be...@apache.org>.
Hi All,
I've checked SHAsums and GPG signature and they are correct.
I've also done some end-to-end comparison to the latest docker image
and there seems to be no regression.
And I'm interested to see the discussion addressing Richard Ellis'
concerns as any post-release changes to the "location" of the new
control (qs -> header) would require a major version (in semver-land).
Thank you,
Donat
On Sat, 12 Sep 2020 at 00:53, Joan Touzet <wo...@apache.org> wrote:
>
> Dear community,
>
> I would like to propose that we release Apache CouchDB 3.1.1.
>
> Changes since the last round:
>
> https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
>
> Candidate release notes:
>
> https://docs.couchdb.org/en/latest/whatsnew/3.1.html
>
> 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!
> (Only PMC members have binding votes, but they depend on community
> feedback to gauge if an official release is ready to be made.)
>
> The release artefacts we are voting on are available here:
>
> https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
>
> There, you will find a tarball, a GPG signature, and SHA256/SHA512
> checksums.
>
> Please follow the test procedure here:
>
>
> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
>
> Please remember that "RC2" is an annotation. If the vote passes, these
> artefacts will be released as Apache CouchDB 3.1.1.
>
> Because of the weekend, this vote will remain open until 5PM ET (UTC-4),
> Tuesday, 15 September 2020.
>
> Please cast your votes now.
>
> Thanks,
> Joan "once more unto the breech, dear friends" Touzet
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Joan Touzet <wo...@apache.org>.
On 16/09/2020 09:05, Bessenyei Balázs Donát wrote:
>> Why should we remove this? I don’t think it is controversial.
>
> Does that mean 3.1.1 will be released with the query parameter
> `buffer_response`?
Yes, it is in 3.1.1-RC2.
> Nit:
>> 3.1.1 will not be cut unless 3 +1 votes, minimum, arrive from committers, with no blockers by convention.
>
> According to http://www.apache.org/legal/release-policy.html#release-approval
> I thought it has to be 3 PMC members (which by the way I think is
> already passed if Nick, Glynn and Joan (RM) are all +1).
> Or is there a different process in CouchDB?
Sorry, correct, fumble on my part. Kinda busy. Voting process is all
detailed here:
https://couchdb.apache.org/bylaws.html
Lazy majority PMC members have binding votes.
-Joan
>
>
> Thank you,
> Donat
>
>
> On Tue, 15 Sep 2020 at 20:32, Joan Touzet <wo...@apache.org> wrote:
>>
>> FYI, Linux packages in test form are available now at
>>
>> https://repo-nightly.couchdb.org/3.x/
>>
>> As always, subject to removal, do not use in production, etc.
>>
>> Windows build will probably land tomorrow, I'm fairly busy today.
>>
>> -Joan
>>
>> On 15/09/2020 08:26, Will Holley wrote:
>>> Environment:
>>> RHEL 8
>>> Elixir: 1.9.1
>>> Erlang: 20.3.8.25
>>>
>>> CPU Architectures: amd64, ppc64le, s390x
>>>
>>> Sig: ok
>>> Checksums: ok
>>> Configure, make & make check: ok
>>> Build release, add admin & start: ok
>>> Used Fauxton to:
>>> - configure cluster: ok
>>> - verify install: ok
>>> - create dbs: ok
>>> - create docs: ok
>>> - create replications between dbs on same cluster: ok
>>> - links to docs: ok
>>>
>>> +1
>>>
>>> On Tue, 15 Sep 2020 at 05:20, Nick Vatamaniuc <va...@gmail.com> wrote:
>>>
>>>> Environment:
>>>> Ubuntu 18.04.5, x86_64
>>>> $ asdf current
>>>> elixir 1.9.4-otp-22
>>>> erlang 22.2.3
>>>> $ cat /etc/apt/sources.list.d/couchdb-bintray.list
>>>> deb https://apache.bintray.com/couchdb-deb bionic main
>>>>
>>>> Sig: ok
>>>> Checksums: ok
>>>> Configure, make & make check: ok
>>>> Build release, add admin & start: ok
>>>> Used Fauxton to:
>>>> - configure cluster: ok
>>>> - verify install: ok
>>>> - create dbs: ok
>>>> - create docs: ok
>>>> - create replications between dbs on same cluster: ok
>>>> - links to docs: ok
>>>>
>>>> +1
>>>>
>>>> Thank you for creating the release, Joan!
>>>>
>>>> -Nick
>>>>
>>>> On Mon, Sep 14, 2020 at 10:15 PM Joan Touzet <wo...@apache.org> wrote:
>>>>>
>>>>> Hi everyone,
>>>>>
>>>>> There have been no votes on this release. Are people available to try it
>>>>> out? Tomorrow, I will be able to complete the binary builds and submit
>>>>> my own vote.
>>>>>
>>>>> Remember, 3.1.1 will not be cut unless 3 +1 votes, minimum, arrive from
>>>>> committers, with no blockers by convention. The Mac situation needs to
>>>>> be investigated. It's not clear to me that there is consensus on
>>>>> blocking the release on the new request header toggle, but if there is,
>>>>> I could cut a 3.1.1-RC3 _without_ that change tomorrow if consensus
>>>>> materialises overnight.
>>>>>
>>>>> Note that I will be on holiday starting end of the week for 2.5 weeks.
>>>>> If 3.1.1 doesn't cut from this RC, for whatever reason, the next
>>>>> opportunity I will have to turn the crank will be 5 October 2020.
>>>>>
>>>>> -Joan
>>>>>
>>>>> On 2020-09-11 6:53 p.m., Joan Touzet wrote:
>>>>>> Dear community,
>>>>>>
>>>>>> I would like to propose that we release Apache CouchDB 3.1.1.
>>>>>>
>>>>>> Changes since the last round:
>>>>>>
>>>>>> https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
>>>>>>
>>>>>> Candidate release notes:
>>>>>>
>>>>>> https://docs.couchdb.org/en/latest/whatsnew/3.1.html
>>>>>>
>>>>>> 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!
>>>>>> (Only PMC members have binding votes, but they depend on community
>>>>>> feedback to gauge if an official release is ready to be made.)
>>>>>>
>>>>>> The release artefacts we are voting on are available here:
>>>>>>
>>>>>> https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
>>>>>>
>>>>>> There, you will find a tarball, a GPG signature, and SHA256/SHA512
>>>>>> checksums.
>>>>>>
>>>>>> Please follow the test procedure here:
>>>>>>
>>>>>>
>>>>>>
>>>> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
>>>>>>
>>>>>>
>>>>>> Please remember that "RC2" is an annotation. If the vote passes, these
>>>>>> artefacts will be released as Apache CouchDB 3.1.1.
>>>>>>
>>>>>> Because of the weekend, this vote will remain open until 5PM ET
>>>> (UTC-4),
>>>>>> Tuesday, 15 September 2020.
>>>>>>
>>>>>> Please cast your votes now.
>>>>>>
>>>>>> Thanks,
>>>>>> Joan "once more unto the breech, dear friends" Touzet
>>>>
>>>
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Bessenyei Balázs Donát <be...@apache.org>.
> Why should we remove this? I don’t think it is controversial.
Does that mean 3.1.1 will be released with the query parameter
`buffer_response`?
Nit:
> 3.1.1 will not be cut unless 3 +1 votes, minimum, arrive from committers, with no blockers by convention.
According to http://www.apache.org/legal/release-policy.html#release-approval
I thought it has to be 3 PMC members (which by the way I think is
already passed if Nick, Glynn and Joan (RM) are all +1).
Or is there a different process in CouchDB?
Thank you,
Donat
On Tue, 15 Sep 2020 at 20:32, Joan Touzet <wo...@apache.org> wrote:
>
> FYI, Linux packages in test form are available now at
>
> https://repo-nightly.couchdb.org/3.x/
>
> As always, subject to removal, do not use in production, etc.
>
> Windows build will probably land tomorrow, I'm fairly busy today.
>
> -Joan
>
> On 15/09/2020 08:26, Will Holley wrote:
> > Environment:
> > RHEL 8
> > Elixir: 1.9.1
> > Erlang: 20.3.8.25
> >
> > CPU Architectures: amd64, ppc64le, s390x
> >
> > Sig: ok
> > Checksums: ok
> > Configure, make & make check: ok
> > Build release, add admin & start: ok
> > Used Fauxton to:
> > - configure cluster: ok
> > - verify install: ok
> > - create dbs: ok
> > - create docs: ok
> > - create replications between dbs on same cluster: ok
> > - links to docs: ok
> >
> > +1
> >
> > On Tue, 15 Sep 2020 at 05:20, Nick Vatamaniuc <va...@gmail.com> wrote:
> >
> >> Environment:
> >> Ubuntu 18.04.5, x86_64
> >> $ asdf current
> >> elixir 1.9.4-otp-22
> >> erlang 22.2.3
> >> $ cat /etc/apt/sources.list.d/couchdb-bintray.list
> >> deb https://apache.bintray.com/couchdb-deb bionic main
> >>
> >> Sig: ok
> >> Checksums: ok
> >> Configure, make & make check: ok
> >> Build release, add admin & start: ok
> >> Used Fauxton to:
> >> - configure cluster: ok
> >> - verify install: ok
> >> - create dbs: ok
> >> - create docs: ok
> >> - create replications between dbs on same cluster: ok
> >> - links to docs: ok
> >>
> >> +1
> >>
> >> Thank you for creating the release, Joan!
> >>
> >> -Nick
> >>
> >> On Mon, Sep 14, 2020 at 10:15 PM Joan Touzet <wo...@apache.org> wrote:
> >>>
> >>> Hi everyone,
> >>>
> >>> There have been no votes on this release. Are people available to try it
> >>> out? Tomorrow, I will be able to complete the binary builds and submit
> >>> my own vote.
> >>>
> >>> Remember, 3.1.1 will not be cut unless 3 +1 votes, minimum, arrive from
> >>> committers, with no blockers by convention. The Mac situation needs to
> >>> be investigated. It's not clear to me that there is consensus on
> >>> blocking the release on the new request header toggle, but if there is,
> >>> I could cut a 3.1.1-RC3 _without_ that change tomorrow if consensus
> >>> materialises overnight.
> >>>
> >>> Note that I will be on holiday starting end of the week for 2.5 weeks.
> >>> If 3.1.1 doesn't cut from this RC, for whatever reason, the next
> >>> opportunity I will have to turn the crank will be 5 October 2020.
> >>>
> >>> -Joan
> >>>
> >>> On 2020-09-11 6:53 p.m., Joan Touzet wrote:
> >>>> Dear community,
> >>>>
> >>>> I would like to propose that we release Apache CouchDB 3.1.1.
> >>>>
> >>>> Changes since the last round:
> >>>>
> >>>> https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
> >>>>
> >>>> Candidate release notes:
> >>>>
> >>>> https://docs.couchdb.org/en/latest/whatsnew/3.1.html
> >>>>
> >>>> 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!
> >>>> (Only PMC members have binding votes, but they depend on community
> >>>> feedback to gauge if an official release is ready to be made.)
> >>>>
> >>>> The release artefacts we are voting on are available here:
> >>>>
> >>>> https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
> >>>>
> >>>> There, you will find a tarball, a GPG signature, and SHA256/SHA512
> >>>> checksums.
> >>>>
> >>>> Please follow the test procedure here:
> >>>>
> >>>>
> >>>>
> >> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
> >>>>
> >>>>
> >>>> Please remember that "RC2" is an annotation. If the vote passes, these
> >>>> artefacts will be released as Apache CouchDB 3.1.1.
> >>>>
> >>>> Because of the weekend, this vote will remain open until 5PM ET
> >> (UTC-4),
> >>>> Tuesday, 15 September 2020.
> >>>>
> >>>> Please cast your votes now.
> >>>>
> >>>> Thanks,
> >>>> Joan "once more unto the breech, dear friends" Touzet
> >>
> >
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Joan Touzet <wo...@apache.org>.
FYI, Linux packages in test form are available now at
https://repo-nightly.couchdb.org/3.x/
As always, subject to removal, do not use in production, etc.
Windows build will probably land tomorrow, I'm fairly busy today.
-Joan
On 15/09/2020 08:26, Will Holley wrote:
> Environment:
> RHEL 8
> Elixir: 1.9.1
> Erlang: 20.3.8.25
>
> CPU Architectures: amd64, ppc64le, s390x
>
> Sig: ok
> Checksums: ok
> Configure, make & make check: ok
> Build release, add admin & start: ok
> Used Fauxton to:
> - configure cluster: ok
> - verify install: ok
> - create dbs: ok
> - create docs: ok
> - create replications between dbs on same cluster: ok
> - links to docs: ok
>
> +1
>
> On Tue, 15 Sep 2020 at 05:20, Nick Vatamaniuc <va...@gmail.com> wrote:
>
>> Environment:
>> Ubuntu 18.04.5, x86_64
>> $ asdf current
>> elixir 1.9.4-otp-22
>> erlang 22.2.3
>> $ cat /etc/apt/sources.list.d/couchdb-bintray.list
>> deb https://apache.bintray.com/couchdb-deb bionic main
>>
>> Sig: ok
>> Checksums: ok
>> Configure, make & make check: ok
>> Build release, add admin & start: ok
>> Used Fauxton to:
>> - configure cluster: ok
>> - verify install: ok
>> - create dbs: ok
>> - create docs: ok
>> - create replications between dbs on same cluster: ok
>> - links to docs: ok
>>
>> +1
>>
>> Thank you for creating the release, Joan!
>>
>> -Nick
>>
>> On Mon, Sep 14, 2020 at 10:15 PM Joan Touzet <wo...@apache.org> wrote:
>>>
>>> Hi everyone,
>>>
>>> There have been no votes on this release. Are people available to try it
>>> out? Tomorrow, I will be able to complete the binary builds and submit
>>> my own vote.
>>>
>>> Remember, 3.1.1 will not be cut unless 3 +1 votes, minimum, arrive from
>>> committers, with no blockers by convention. The Mac situation needs to
>>> be investigated. It's not clear to me that there is consensus on
>>> blocking the release on the new request header toggle, but if there is,
>>> I could cut a 3.1.1-RC3 _without_ that change tomorrow if consensus
>>> materialises overnight.
>>>
>>> Note that I will be on holiday starting end of the week for 2.5 weeks.
>>> If 3.1.1 doesn't cut from this RC, for whatever reason, the next
>>> opportunity I will have to turn the crank will be 5 October 2020.
>>>
>>> -Joan
>>>
>>> On 2020-09-11 6:53 p.m., Joan Touzet wrote:
>>>> Dear community,
>>>>
>>>> I would like to propose that we release Apache CouchDB 3.1.1.
>>>>
>>>> Changes since the last round:
>>>>
>>>> https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
>>>>
>>>> Candidate release notes:
>>>>
>>>> https://docs.couchdb.org/en/latest/whatsnew/3.1.html
>>>>
>>>> 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!
>>>> (Only PMC members have binding votes, but they depend on community
>>>> feedback to gauge if an official release is ready to be made.)
>>>>
>>>> The release artefacts we are voting on are available here:
>>>>
>>>> https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
>>>>
>>>> There, you will find a tarball, a GPG signature, and SHA256/SHA512
>>>> checksums.
>>>>
>>>> Please follow the test procedure here:
>>>>
>>>>
>>>>
>> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
>>>>
>>>>
>>>> Please remember that "RC2" is an annotation. If the vote passes, these
>>>> artefacts will be released as Apache CouchDB 3.1.1.
>>>>
>>>> Because of the weekend, this vote will remain open until 5PM ET
>> (UTC-4),
>>>> Tuesday, 15 September 2020.
>>>>
>>>> Please cast your votes now.
>>>>
>>>> Thanks,
>>>> Joan "once more unto the breech, dear friends" Touzet
>>
>
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Will Holley <wi...@gmail.com>.
Environment:
RHEL 8
Elixir: 1.9.1
Erlang: 20.3.8.25
CPU Architectures: amd64, ppc64le, s390x
Sig: ok
Checksums: ok
Configure, make & make check: ok
Build release, add admin & start: ok
Used Fauxton to:
- configure cluster: ok
- verify install: ok
- create dbs: ok
- create docs: ok
- create replications between dbs on same cluster: ok
- links to docs: ok
+1
On Tue, 15 Sep 2020 at 05:20, Nick Vatamaniuc <va...@gmail.com> wrote:
> Environment:
> Ubuntu 18.04.5, x86_64
> $ asdf current
> elixir 1.9.4-otp-22
> erlang 22.2.3
> $ cat /etc/apt/sources.list.d/couchdb-bintray.list
> deb https://apache.bintray.com/couchdb-deb bionic main
>
> Sig: ok
> Checksums: ok
> Configure, make & make check: ok
> Build release, add admin & start: ok
> Used Fauxton to:
> - configure cluster: ok
> - verify install: ok
> - create dbs: ok
> - create docs: ok
> - create replications between dbs on same cluster: ok
> - links to docs: ok
>
> +1
>
> Thank you for creating the release, Joan!
>
> -Nick
>
> On Mon, Sep 14, 2020 at 10:15 PM Joan Touzet <wo...@apache.org> wrote:
> >
> > Hi everyone,
> >
> > There have been no votes on this release. Are people available to try it
> > out? Tomorrow, I will be able to complete the binary builds and submit
> > my own vote.
> >
> > Remember, 3.1.1 will not be cut unless 3 +1 votes, minimum, arrive from
> > committers, with no blockers by convention. The Mac situation needs to
> > be investigated. It's not clear to me that there is consensus on
> > blocking the release on the new request header toggle, but if there is,
> > I could cut a 3.1.1-RC3 _without_ that change tomorrow if consensus
> > materialises overnight.
> >
> > Note that I will be on holiday starting end of the week for 2.5 weeks.
> > If 3.1.1 doesn't cut from this RC, for whatever reason, the next
> > opportunity I will have to turn the crank will be 5 October 2020.
> >
> > -Joan
> >
> > On 2020-09-11 6:53 p.m., Joan Touzet wrote:
> > > Dear community,
> > >
> > > I would like to propose that we release Apache CouchDB 3.1.1.
> > >
> > > Changes since the last round:
> > >
> > > https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
> > >
> > > Candidate release notes:
> > >
> > > https://docs.couchdb.org/en/latest/whatsnew/3.1.html
> > >
> > > 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!
> > > (Only PMC members have binding votes, but they depend on community
> > > feedback to gauge if an official release is ready to be made.)
> > >
> > > The release artefacts we are voting on are available here:
> > >
> > > https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
> > >
> > > There, you will find a tarball, a GPG signature, and SHA256/SHA512
> > > checksums.
> > >
> > > Please follow the test procedure here:
> > >
> > >
> > >
> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
> > >
> > >
> > > Please remember that "RC2" is an annotation. If the vote passes, these
> > > artefacts will be released as Apache CouchDB 3.1.1.
> > >
> > > Because of the weekend, this vote will remain open until 5PM ET
> (UTC-4),
> > > Tuesday, 15 September 2020.
> > >
> > > Please cast your votes now.
> > >
> > > Thanks,
> > > Joan "once more unto the breech, dear friends" Touzet
>
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Nick Vatamaniuc <va...@gmail.com>.
Environment:
Ubuntu 18.04.5, x86_64
$ asdf current
elixir 1.9.4-otp-22
erlang 22.2.3
$ cat /etc/apt/sources.list.d/couchdb-bintray.list
deb https://apache.bintray.com/couchdb-deb bionic main
Sig: ok
Checksums: ok
Configure, make & make check: ok
Build release, add admin & start: ok
Used Fauxton to:
- configure cluster: ok
- verify install: ok
- create dbs: ok
- create docs: ok
- create replications between dbs on same cluster: ok
- links to docs: ok
+1
Thank you for creating the release, Joan!
-Nick
On Mon, Sep 14, 2020 at 10:15 PM Joan Touzet <wo...@apache.org> wrote:
>
> Hi everyone,
>
> There have been no votes on this release. Are people available to try it
> out? Tomorrow, I will be able to complete the binary builds and submit
> my own vote.
>
> Remember, 3.1.1 will not be cut unless 3 +1 votes, minimum, arrive from
> committers, with no blockers by convention. The Mac situation needs to
> be investigated. It's not clear to me that there is consensus on
> blocking the release on the new request header toggle, but if there is,
> I could cut a 3.1.1-RC3 _without_ that change tomorrow if consensus
> materialises overnight.
>
> Note that I will be on holiday starting end of the week for 2.5 weeks.
> If 3.1.1 doesn't cut from this RC, for whatever reason, the next
> opportunity I will have to turn the crank will be 5 October 2020.
>
> -Joan
>
> On 2020-09-11 6:53 p.m., Joan Touzet wrote:
> > Dear community,
> >
> > I would like to propose that we release Apache CouchDB 3.1.1.
> >
> > Changes since the last round:
> >
> > https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
> >
> > Candidate release notes:
> >
> > https://docs.couchdb.org/en/latest/whatsnew/3.1.html
> >
> > 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!
> > (Only PMC members have binding votes, but they depend on community
> > feedback to gauge if an official release is ready to be made.)
> >
> > The release artefacts we are voting on are available here:
> >
> > https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
> >
> > There, you will find a tarball, a GPG signature, and SHA256/SHA512
> > checksums.
> >
> > Please follow the test procedure here:
> >
> >
> > https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
> >
> >
> > Please remember that "RC2" is an annotation. If the vote passes, these
> > artefacts will be released as Apache CouchDB 3.1.1.
> >
> > Because of the weekend, this vote will remain open until 5PM ET (UTC-4),
> > Tuesday, 15 September 2020.
> >
> > Please cast your votes now.
> >
> > Thanks,
> > Joan "once more unto the breech, dear friends" Touzet
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Joan Touzet <wo...@apache.org>.
That's fine by me, would rather not have a DOA release.
A fix is going in to bypass ppc64le builds for now, then hopefully
Jenkins will have Linux binary builds up for testing. I hope to get to a
Windows build today, too.
-Joan
On 15/09/2020 11:44, Jan Lehnardt wrote:
> Hey all,
>
> I’ll able to look into the Mac build and binaries on Thursday. I hope nobody minds extending the VOTE until then.
>
> Thanks!
> Jan
> —
>
>> On 15. Sep 2020, at 04:15, Joan Touzet <wo...@apache.org> wrote:
>>
>> Hi everyone,
>>
>> There have been no votes on this release. Are people available to try it out? Tomorrow, I will be able to complete the binary builds and submit my own vote.
>>
>> Remember, 3.1.1 will not be cut unless 3 +1 votes, minimum, arrive from committers, with no blockers by convention. The Mac situation needs to be investigated. It's not clear to me that there is consensus on blocking the release on the new request header toggle, but if there is, I could cut a 3.1.1-RC3 _without_ that change tomorrow if consensus materialises overnight.
>>
>> Note that I will be on holiday starting end of the week for 2.5 weeks. If 3.1.1 doesn't cut from this RC, for whatever reason, the next opportunity I will have to turn the crank will be 5 October 2020.
>>
>> -Joan
>>
>> On 2020-09-11 6:53 p.m., Joan Touzet wrote:
>>> Dear community,
>>> I would like to propose that we release Apache CouchDB 3.1.1.
>>> Changes since the last round:
>>> https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
>>> Candidate release notes:
>>> https://docs.couchdb.org/en/latest/whatsnew/3.1.html
>>> 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! (Only PMC members have binding votes, but they depend on community feedback to gauge if an official release is ready to be made.)
>>> The release artefacts we are voting on are available here:
>>> https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
>>> There, you will find a tarball, a GPG signature, and SHA256/SHA512 checksums.
>>> Please follow the test procedure here:
>>> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release Please remember that "RC2" is an annotation. If the vote passes, these artefacts will be released as Apache CouchDB 3.1.1.
>>> Because of the weekend, this vote will remain open until 5PM ET (UTC-4), Tuesday, 15 September 2020.
>>> Please cast your votes now.
>>> Thanks,
>>> Joan "once more unto the breech, dear friends" Touzet
>
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Jan Lehnardt <ja...@apache.org>.
Hey all,
I’ll able to look into the Mac build and binaries on Thursday. I hope nobody minds extending the VOTE until then.
Thanks!
Jan
—
> On 15. Sep 2020, at 04:15, Joan Touzet <wo...@apache.org> wrote:
>
> Hi everyone,
>
> There have been no votes on this release. Are people available to try it out? Tomorrow, I will be able to complete the binary builds and submit my own vote.
>
> Remember, 3.1.1 will not be cut unless 3 +1 votes, minimum, arrive from committers, with no blockers by convention. The Mac situation needs to be investigated. It's not clear to me that there is consensus on blocking the release on the new request header toggle, but if there is, I could cut a 3.1.1-RC3 _without_ that change tomorrow if consensus materialises overnight.
>
> Note that I will be on holiday starting end of the week for 2.5 weeks. If 3.1.1 doesn't cut from this RC, for whatever reason, the next opportunity I will have to turn the crank will be 5 October 2020.
>
> -Joan
>
> On 2020-09-11 6:53 p.m., Joan Touzet wrote:
>> Dear community,
>> I would like to propose that we release Apache CouchDB 3.1.1.
>> Changes since the last round:
>> https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
>> Candidate release notes:
>> https://docs.couchdb.org/en/latest/whatsnew/3.1.html
>> 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! (Only PMC members have binding votes, but they depend on community feedback to gauge if an official release is ready to be made.)
>> The release artefacts we are voting on are available here:
>> https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
>> There, you will find a tarball, a GPG signature, and SHA256/SHA512 checksums.
>> Please follow the test procedure here:
>> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release Please remember that "RC2" is an annotation. If the vote passes, these artefacts will be released as Apache CouchDB 3.1.1.
>> Because of the weekend, this vote will remain open until 5PM ET (UTC-4), Tuesday, 15 September 2020.
>> Please cast your votes now.
>> Thanks,
>> Joan "once more unto the breech, dear friends" Touzet
Re: [VOTE] Release Apache CouchDB 3.1.1 (RC2)
Posted by Joan Touzet <wo...@apache.org>.
Hi everyone,
There have been no votes on this release. Are people available to try it
out? Tomorrow, I will be able to complete the binary builds and submit
my own vote.
Remember, 3.1.1 will not be cut unless 3 +1 votes, minimum, arrive from
committers, with no blockers by convention. The Mac situation needs to
be investigated. It's not clear to me that there is consensus on
blocking the release on the new request header toggle, but if there is,
I could cut a 3.1.1-RC3 _without_ that change tomorrow if consensus
materialises overnight.
Note that I will be on holiday starting end of the week for 2.5 weeks.
If 3.1.1 doesn't cut from this RC, for whatever reason, the next
opportunity I will have to turn the crank will be 5 October 2020.
-Joan
On 2020-09-11 6:53 p.m., Joan Touzet wrote:
> Dear community,
>
> I would like to propose that we release Apache CouchDB 3.1.1.
>
> Changes since the last round:
>
> https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
>
> Candidate release notes:
>
> https://docs.couchdb.org/en/latest/whatsnew/3.1.html
>
> 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!
> (Only PMC members have binding votes, but they depend on community
> feedback to gauge if an official release is ready to be made.)
>
> The release artefacts we are voting on are available here:
>
> https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
>
> There, you will find a tarball, a GPG signature, and SHA256/SHA512
> checksums.
>
> Please follow the test procedure here:
>
>
> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
>
>
> Please remember that "RC2" is an annotation. If the vote passes, these
> artefacts will be released as Apache CouchDB 3.1.1.
>
> Because of the weekend, this vote will remain open until 5PM ET (UTC-4),
> Tuesday, 15 September 2020.
>
> Please cast your votes now.
>
> Thanks,
> Joan "once more unto the breech, dear friends" Touzet
[RESULT] (was: [VOTE] Release Apache CouchDB 3.1.1 (RC2))
Posted by Joan Touzet <wo...@apache.org>.
Dear community,
The vote has now closed.
Thank you to everyone who participated!
The results are:
+1 - 4 votes
+0 - 0 votes
-0 - 0 votes
-1 - 0 votes
The vote is PASSED.
Thanks,
Joan
On 11/09/2020 18:53, Joan Touzet wrote:
> Dear community,
>
> I would like to propose that we release Apache CouchDB 3.1.1.
>
> Changes since the last round:
>
> https://github.com/apache/couchdb/compare/3.1.1-RC1...3.1.1-RC2
>
> Candidate release notes:
>
> https://docs.couchdb.org/en/latest/whatsnew/3.1.html
>
> 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!
> (Only PMC members have binding votes, but they depend on community
> feedback to gauge if an official release is ready to be made.)
>
> The release artefacts we are voting on are available here:
>
> https://dist.apache.org/repos/dist/dev/couchdb/source/3.1.1/rc.2/
>
> There, you will find a tarball, a GPG signature, and SHA256/SHA512
> checksums.
>
> Please follow the test procedure here:
>
>
> https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
>
>
> Please remember that "RC2" is an annotation. If the vote passes, these
> artefacts will be released as Apache CouchDB 3.1.1.
>
> Because of the weekend, this vote will remain open until 5PM ET (UTC-4),
> Tuesday, 15 September 2020.
>
> Please cast your votes now.
>
> Thanks,
> Joan "once more unto the breech, dear friends" Touzet