My results: +1

Tarball checksums match
Windows 10 x64 build successful
All tests pass, first try
Windows installer build successful
Install on Windows 7 x64 successful

curl localhost:5984 results: {"couchdb":"Welcome","version":"3.0.0","git_sha":"03a77db6c","uuid":"5d8a899d161d5b7c7ccc4ca9c875fe15","features":["access-ready","partitioned","pluggable-storage-engines","reshard","scheduler"],"vendor":{"name":"The Apache Software Foundation"}}
Fauxton Validate Install also passes.

Windows installer now available at:

  https://dist.apache.org/repos/dist/dev/couchdb/binary/win/3.0.0/rc.3/

Linux packages available at:

  https://repo-nightly.couchdb.org/3.0.x/

-Joan

On 2020-02-19 19:16, Joan Touzet wrote:
Dear community,

I would like to propose that we release Apache CouchDB 3.0.0.

Changes since last time:

     https://github.com/apache/couchdb/compare/3.0.0-RC2...3.0.0-RC3

Candidate release notes:

     https://docs.couchdb.org/en/latest/whatsnew/3.0.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.0.0/rc.3

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 "RC3" is an annotation. If the vote passes, these artefacts will be released as Apache CouchDB 3.0.0.

Please cast your votes now.

Thanks,
Joan "something something Lionel Ritchie" Touzet

P.S. I'm off for a few hours but will have Windows and Linux binaries tonight, before I'm gone for the weekend. Our schedule for next week remains unchanged - Tuesday push, Wednesday release.

Reply via email to