Stefan Sperling wrote on Fri, 14 Feb 2020 14:40 +00:00: > On Fri, Feb 14, 2020 at 02:22:10PM +0000, Daniel Shahaf wrote: > > One addition: Shall we announce that 1.10.x will be end-of-life 24 > > months after 1.14.0-GA? 1.10.0 was released on 2018-10-30. > > The current release schedule offers 4 years of support for 1.10 so it > becomes obsolete after 2022-10-30. It would be good if we held the > promise we gave and kept supporting 1.10 at least until then. >
I think we only introduced that promise after 1.10, but nevertheless, it makes sense to honour it. > However, we have traditionally supported two lines of releases, one > for every fix and an older one with just the critical fixes, which is > also what I would propose for our new release schedule because it > gives users time to migrate from one stable release to the next one. > In this case 1.10 would be supported with critical fixes until 1.15 is > released, possibly beyond 2022-10-30. I think I would prefer this if > we can manage to do so. > > Hmm. We could simply leave this question open until 2022-10-30 :-) If we don't release 1.15.0 by 2022-10-30, perhaps we can on that date switch to supporting two flavours of 1.14.x, one that's the usual "for every fix" and another that's "1.14.0 + critical fixes only". That might be easier than supporting a 4+-years-old 1.10.0 into the future. But yeah, we can discuss this again closer to the date — unless there are svn_version.h API changes we should make today to make that possible? Cheers, Daniel