subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Shahaf <...@daniel.shahaf.name>
Subject Re: Release Management, Subversion 1.14
Date Fri, 14 Feb 2020 14:22:10 GMT
Stefan Sperling wrote on Fri, 14 Feb 2020 14:05 +0100:
> On Fri, Feb 14, 2020 at 07:36:43AM -0500, Nathan Hartman wrote:
> > On Fri, Feb 14, 2020 at 7:26 AM Stefan Sperling <stsp@elego.de> wrote:
> >   
> > > - Release notes and CHANGES need to be updated.
> > >   There are relatively few changes since we only have to document what
> > >   changed since September. I am wondering if 1.14 release note should
> > >   summarize what occurred betwen 1.10 and 1.14, or if they should be
> > >   written relative to 1.13 as the current draft implies.
> > >   For users upgrading from LTS to LTS it might make sense to give an
> > >   overview of what changed on one page. And it would also give us more
> > >   material to fill the release notes page with :)
> > >  
> > 
> > I was thinking about this a few days ago. I think that LTS releases are a
> > different "line" and the release notes should include changes since 1.10.
> > If the community agrees with that, I'll work on it.  
> 
> In my opinion that would be great. Thanks!
> 

My first preference would have been to keep 1.14 written against 1.13,
since that's the simplest solution.

In the alternative, I'm concerned about duplication between
1.{11,12,13}.html on the one hand and 1.14.html on the other hand.
I think that could be addressed by using server-side includes, as we
already do for the navigation bar, so the content would be written once
and included by both 1.x.html (11 ≤ x ≤ 13) and 1.14.html.  Makes sense?

> I guess we could plan to issue new 1.10.x and 1.14.x releases every 6 months,
> with any critical fixes (security or data corruption) getting released as soon
> as possible. 1.15 would happen only if new APIs must be introduced to fix a
> problem, or if new APIs have been introduced with new features added within
> the previous 6 months cycle. Until 1.15 happens we support 1.10 and 1.14.
> Once 1.15 appears, we support 1.14 and 1.15 until 1.16 appears, and so on.
> 
> Would this work?

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.

Cheers,

Daniel

Mime
View raw message