Hi, Our convenience binaries are using Erlang 20, and we are now seeing users file bug reports for issues that have been fixed by the Erlang team more than 3 years ago :( In recent years the Erlang/OTP team has accelerated their release cycles, and we are now _way_ behind the current Erlang 24.2 release.
I took a peek at the RabbitMQ official image history, and it seems the Docker folks are rebuilding and publishing images for supported RabbitMQ versions to use the newest Erlang/OTP on the day it’s released. That’s aggressive! But I am thinking that we might want to head toward that general direction and give users a CouchDB install that packages the current Erlang version by default. One question I had in my head was whether to publish packages / images for multiple major Erlang versions, but it doesn’t seem to be a common practice. I also wondered whether to pin a given CouchDB release to an Erlang release series, e.g. CouchDB 3.2.0 packages are built against the latest Erlang 20 patch release, while 3.2.1 could jump to Erlang 24. I think the cognitive load for debugging support tickets might be lower in that approach. What do you think? Adam
