On Fri, Feb 13, 2026 at 9:52 AM Evgeny Kotkov <[email protected]> wrote:
> Nathan Hartman <[email protected]> writes: > > > May I suggest (warning: bikeshed ahead): > > > > - Only release line N receives full support. > > > > - Release lines {N-1, N-2, …} receive security-only support and > > critical bugfixes (e.g., corruption). > > > > My rationale for limiting full support to release line N is that > > during that time, we're (hopefully) working towards release line N+1. > > I think it will be more manageable. > > Sounds good to me. > > To recap, this is what the updated policy would look like: > ---------------------------------------------------------- > > Starting with 1.15, all release lines are supported for at least 3 years. > At least one release line is always supported. > > A release line becomes EOL when: > - It has been supported for at least 3 years. > - There is a new minor release line with an age of at least 3 months. > > Among the supported release lines: > - The latest release line ("N") receives full support. > - Other release lines (N-1, N-2, …) receive security-only support and > critical bugfixes, e.g., related to data corruption. > LGTM and +1! > ---------------------------------------------------------- > > From the RM perspective, I'd be willing to move forward with it for 1.15. > So I'm going to propose such release policy change via a separate thread, > to ensure that it gets appropriate attention. > Yes, please do. Thank you so much! Nathan
