[erlang-questions] Patch Package: OTP 19.3.6.4

[derek]

On Thu, Nov 30, 2017 at 1:06 PM, Sverker Eriksson <
sverker.eriksson@REDACTED> wrote:
> All announced patches on 19 will have versions OTP-19.3.6.x

But wait, will there be more 19.3.7+.x versions?

>
> Any other pushed OTP-19 tag is some sort of special customer request
> of backporting fix or feature.

ok, so I think I can skip this OTP-19.2.y.z.

>
> If something is fixed for example on OTP-19.2.y.z, then it will also
> be fixed or already have been fixed on OTP-19.3.6.x.
>
> /Sverker


And Ingela or Sverker can comment on the long term maintenance plan? or
generic rules

https://github.com/nodejs/Release#release-schedule   Something like this
for nodejs, it clearly mentioned Maintenance LTS End for each major node
version;

I just wonder when can I drop support of Erlang 17, 18, ... ?

>
>
> On tor, 2017-11-30 at 12:15 -0800, derek wrote:
>> To Ingela and if sverker also on the list:
>>
>> This morning I just found OTP-19.2.3.1 release is available, for the
>> only changed application is erts-8.2.2.1;  I'm trying to understand
>> why is this needed? when you already have OTP 19.3.6.3 which included
>> erts-8.3.5.3;
>> how many users are there sticking with 19.2 and can upgrade
>> 19.2.X.Y.latest but can't upgrade to 19.3.X.Y.latest  ?
>> as a downstream OS distribution packager, I want to know if this need
>> a packaging as well
>>
>> Could you also talk on what are the Erlang OTP release rules? if not
>> have recorded on some link? and what's the maintenance plan for each
>> past release? how long will each release be supported? like 19 will
>> be
>> supported till Month-Year? 18 till what Month-Year?   and is 17
>> already no longer maintained?
>>
>>
>> https://github.com/erlang/otp/releases
>> https://github.com/erlang/otp/releases/tag/OTP-19.2.3.1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20171201/8bfaba63/attachment.htm>