Stefan Sperling wrote: > On Fri, May 18, 2018 at 02:29:25PM +0100, Julian Foad wrote: > > Branch for stabilization 4 months after the last release (which was in > > 2018-04), so: > > > > * Branch in 2018-08 > > * Aim to release in 2018-10 > > Wouldn't we also have to adjust our backporting guidelines if we > did this?
Yes, certainly we have to adjust our backporting guidelines! > Would 1.10 only receive "security or data corruption > fixes" as of October 2018? No, 1.10 would be designated "LTS" (long term support). Because we haven't previously told users anything, they should assume that 1.10 will be supported over a similar time scale to previous releases. Therefore we should designate 1.10 as LTS, and 1.11 as a standard (non-LTS) release. Definitions something like this: LTS release: * full backports for at least 2 years, and at least until the next LTS release * security/corruption fixes for at least 4 years, and at least until the next-but-one LTS release standard release: * full backports at least until the next standard release * security/corruption fixes at least until the next-but-one standard release Plus a bit extra (e.g. a couple of months) on each of these times. - Julian
