Guilty as charged. I'll roll RC2 in the morning.

Cheers
Jan
—

> On 18. Feb 2019, at 20:09, Nick Vatamaniuc <vatam...@gmail.com> wrote:
> 
> Thanks, Jan!
> 
> Tried it on a Centos 7 VM.
> 
> Signature and hashes look good but after configure step my `make` failed. I
> think rebar was built on a too new of an Erlang release. We should try 20
> or ideally 19.
> 
> ----
> $ make
> Uncaught error in rebar_core: {'EXIT',
> 
> =ERROR REPORT==== 18-Feb-2019::19:07:54 ===
> beam/beam_load.c(1863): Error loading module rebar_getopt:
>  This BEAM file was compiled for a later version of the run-time system
> than 20.
>  To fix this, please recompile this module with an 20 compiler.
>  (Use of opcode 162; this emulator supports only up to 159.)
> ----
> 
> -Nick
> 
> 
>> On Sun, Feb 17, 2019 at 3:05 PM Jan Lehnardt <j...@apache.org> wrote:
>> 
>> Convenience Mac binary is up here:
>> https://dist.apache.org/repos/dist/dev/couchdb/binary/mac/2.3.1/rc.1/
>> 
>>> On 17. Feb 2019, at 19:47, Jan Lehnardt <j...@apache.org> wrote:
>>> 
>>> Dear community,
>>> 
>>> I would like to propose that we release Apache CouchDB 2.3.1-RC1.
>>> 
>>> Candidate release notes:
>>> 
>>>  https://docs.couchdb.org/en/2.3.1/whatsnew/2.3.html#version-2-3-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:
>>> 
>>>   https://dist.apache.org/repos/dist/dev/couchdb/source/2.3.1/rc.1/
>>> 
>>> 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 "RC1" is an annotation. If the vote passes, these
>> artefacts will be released as Apache CouchDB 2.3.1.
>>> 
>>> Please cast your votes now.
>>> 
>>> Thanks,
>>> Jan
>>> —
>> 
>> 

Reply via email to