[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Intentions for 1.11 release timing

From: Julian Foad <julianfoad_at_apache.org>
Date: Fri, 18 May 2018 14:29:25 +0100

Johan Corveleyn wrote:
> I think we need to aim for a much sooner 1.11 release. And I'd like us
> to agree on some intended planning / timing. I know it's easy to talk
> about it, and much more difficult to actually *do it*. But first
> things first, what are our intentions?

Yes, let's agree a plan. Thanks for raising this.

The suggestion below for a 6-month "fast" cycle with 2-year "LTS" releases is in line with what I think we should be doing and what I think we *can* do. On top of that, it is similar to what some other stable software projects do (I'm thinking of Ubuntu).

So I support that plan.

I don't recall any objections outstanding. Yes, of course it will be more difficult initially, and yes, we don't have much capacity, but the idea is that the new plan will improve the situation.

Some details need "fleshing out" (such as what we do if the schedule slips considerably), but that is fine, we can decide those details after the main decision.

> > - WC multiple format support: we're okay for now (1.8 - 1.10 have the
> > same format), but for 1.11 it would be good if we can make
> > better-pristines happen (go Brane! :-).

It would be good, yes, but not a blocker. We can continue without it for the time being. If and when we want or need a format bump, we can figure out what to do at that point.

> > - Frequency: should we aim for 6 months, or 9, 12, ... for the "fast
> > releases" (and "long term support" releases, each a couple of years
> > apart)? I'd stick with my initial proposal: 6 month release cycle, and
> > designate one as an LTS release every 2 years, of which we support one
> > fully, and one more with only security fixes.


> So, IMHO, we just need to pick a date for creating the 1.11.x branch
> (the rest of the timing follows from that), and have some poor soul
> volunteer to RM it :-).

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

(I choose the 1.10 release date rather than branching date as a baseline, because we had much more and much older changes that needed testing, reviewing and fixing. In a 6-month cycle we should be able to stabilize more quickly.)

At this time, I know of no reason why I would not be able to RM 1.11 myself. Otherwise I am happy to lend some support to someone else doing it.

- Julian
Received on 2018-05-18 15:29:30 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.