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
A belated +1 to archiving. Thanks Joan, and also thanks for keeping the
remotes/origin/ioq-per-shard-or-user branch.
-Russell
On Wed, Oct 21, 2020 at 12:27 PM Joan Touzet wrote:
> Hah!
>
> OK, it's all done. At present I cannot remove any of the #.#.# branches
> as Infra has protected them.
Congrats Donat! Welcome aboard!
-Russell
On Fri, Jan 15, 2021 at 10:17 AM Alessio 'Blaster' Biancalana <
dottorblas...@apache.org> wrote:
> Congratulations and welcome!
>
> Alessio
>
> On Fri, Jan 15, 2021 at 4:40 PM Dave Cottlehuber
> wrote:
>
> > > > On 14. Jan 2021, at 21:48, Robert Newson
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
