Nathan Hartman <[email protected]> writes:
> If I understand Evgeny's proposal correctly, it means:
>
> Starting with 1.15, all releases are supported for at least 3 years,
> or until 3 months after the next minor release, whichever is later.
I think this description would be easier to parse if we specify the criteria
when a release becomes EOL (see below).
> It would only support {N-1, N-2, ...} releases if they happened within
> the last 3 years (plus the 3 month overlap).
>
> After that, they become EOL.
>
> Is my understanding correct?
Yes, +1 to that.
However, building on the original suggestion, I think we could also have an
additional variation, distinguishing between "full support" and "security-only
support".
Assuming security-only support requires less maintenance, this acts as a small
escape hatch if we somehow end up with three or more active release lines
simultaneously. Personally, I'm fine with either approach, but there might
be cases when having this variation could be useful.
The whole policy could then be structured as:
------------------------------------------------------------
Starting with 1.15, all releases are supported for at least 3 years.
At least one release line is always supported.
The release line becomes EOL when:
- It has been supported for at least 3 years.
- There is a new minor release with an age of at least 3 months.
Among the supported releases:
- Release lines {N, N-1} receive full support.
- Release lines {N-2, N-3, …} receive security-only support.
Thanks,
Evgeny Kotkov
