Oh that's fantastic, Joan! Glad to hear it. I'm excited to clear out some
of the older Erlang versions, and I would love to see CouchDB and
IBM/Cloudant stay more uptodate on Erlang releases. Thanks for all
the work on the packaging front, that's awesome to see!
-Russell
On Mon, Jan 25, 2021 at
Hey Russell, have no fear. I'm happy to say your 2014 essay is no longer
an issue :)
We've been shipping our couchdb binaries with Erlang Solutions'
pre-built Erlang for a very long time now, at least since 2.1.0 and
possibly since 2.0.0 released. When they don't provide it, we build
using
I'm also +1 to removing Erlang 19.
I wanted to reiterate what Newson said about Erlang Solutions providing
Erlang packaging, and I think we should more strongly lean on options like
this rather than being dependent on the OS distros Erlang versions. Many
years ago I wrote about the nuances with
Thank you all for the input!
I'll remove erlang 19 for `couchdb-config` and we'll be able to refer
to this thread when we have to remove it anywhere else.
Donat
On Sat, Jan 23, 2021 at 10:09 PM Adam Kocoloski wrote:
>
> Ah, good research there Joan. +1 to Donat’s suggestion to drop support
Ah, good research there Joan. +1 to Donat’s suggestion to drop support for 19
from me.
Adam
> On Jan 22, 2021, at 4:49 PM, Joan Touzet wrote:
>
> On 2021-01-22 4:37 p.m., Robert Newson wrote:
>> Iteresting. I’m actually surprised at the inversion here (that CouchDB
>> is dependent on
On 2021-01-22 4:37 p.m., Robert Newson wrote:
Iteresting. I’m actually surprised at the inversion here (that CouchDB is
dependent on IBM to confirm CouchDB’s stability). I’ve always agonised over
even the perception that IBM/Cloudant is calling the shots. I appreciate the
reassurance
+1 on dropping Erlang 19
It's been a best-effort support for it anyway, if I remember the last
discussion about it correctly.
I looked at the failure in the CI and it looks like we're failing on
the ceil/1 function in couch_emsort.erl. We already shipped 3.1.1 with
that change and the commit is
Iteresting. I’m actually surprised at the inversion here (that CouchDB is
dependent on IBM to confirm CouchDB’s stability). I’ve always agonised over
even the perception that IBM/Cloudant is calling the shots. I appreciate the
reassurance that running at scale provides, of course, I just
On 22/01/2021 15:48, Robert Newson wrote:
> I’m +1 on dropping Erlang 19 support. Erlang is now on major release 23.
No problem here.
> I’d further advocate a general policy of supporting only the most recent 2 or
> 3 major releases of Erlang/OTP.
>
> The main (I think only?) reason to keep
I’m +1 on dropping Erlang 19 support. Erlang is now on major release 23.
I’d further advocate a general policy of supporting only the most recent 2 or 3
major releases of Erlang/OTP.
The main (I think only?) reason to keep compatibility so far back is because of
the versions supported by some
Hi All,
CI for https://github.com/apache/couchdb-config appears to be broken.
I wanted to fix it in
https://github.com/apache/couchdb-config/pull/34/files , but I'm
getting issues with erlang 19. Are we okay with dropping 19 support
there?
On a different note: are we okay with dropping erlang 19
11 matches
Mail list logo
