After tagging the new 3.4.0 release, but before announcing it and
publishing the binaries, we discovered an issue where the new password
auto-upgrade setting could lock out users from a _users db during
downgrade. We discussed it on dev slack channel and deemed that it's
not ideal as we normally strive to allow safely downgrading back to a
previous version.
Since we already tagged 3.4.0 we decided to create a new 3.4.1 release
and will end up announcing 3.4.1 and publish binaries for it instead
of 3.4.0.
So this is the RC1 proposal for the new 3.4.1 release:
Candidate release notes:
https://docs.couchdb.org/en/latest/whatsnew/3.4.html#version-3-4-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! (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.4.1/rc1/
There, you will find a tarball, a GPG signature, and the SHA256 checksum.
Please follow the test procedure here:
https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
Please remember that "RC1" is an annotation. If the vote passes, these
artefacts will be released as Apache CouchDB 3.4.1.
Please cast your votes now.
Thanks,
-Nick
