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

Re: Release Management, Subversion 1.14

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 14 Feb 2020 13:26:27 +0100

On Fri, Jan 24, 2020 at 12:22:19PM +0100, Stefan Sperling wrote:
> On Fri, Jan 24, 2020 at 10:47:49AM +0000, Julian Foad wrote:
> > Please can someone volunteer to be the release manager for Subversion 1.14?
> >
> > I won't be able to do that myself, although I will gladly help and advise.
> >
> > My starting suggestions include:
> > - assume 1.14 is going to proceed as an LTS release under the current
> > release schedule,
> > - choose and publish proposed dates for branching etc.,
> > - discuss with the dev community what changes, if any, we might want to
> > get in for 1.14, including documentation especially the release notes, and
> > get those moving,
> > - also consider whether any backport releases are needed.
> I agree with the above plan and I will try to handle the RM role if nobody
> else volunteers.
> Since you no longer have time to drive time-based releases we should
> pick up the discussion we had back in October. For reference, my most
> recent statement is archived here:
> https://svn.haxx.se/dev/archive-2019-10/0179.shtml
> Now would be a good time to determine what needs to happen after 1.14 has
> been released. As far as I understand we have now run out of paid development
> resources and need to establish a purely volunteer-driven process that does
> not rely on anyone having more than a handful of hours to spend per

... month (completing the above sentence which was cut short accidentally).

To summarize my understanding of the current state of things:

- We need to decide what should happen with experimental features
  and do the work to make it happen. See the thread titled
  'future of our "experimental" features' for more information.

- 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 :)

- We need to branch 1.14.x very soon or we'll miss the 4-week soak window.
  Perhaps the release date should be pushed back to allow us to complete
  the above tasks at a slow pace?

- We need to decide what happens after 1.14. It would make sense to have a
  new plan agreed upon. If we don't decide on anything we'll end up with a
  1.15 release planned for October 2020. I doubt this plan is still viable
  given how little is happening right now in order to prepare 1.14.
Received on 2020-02-14 13:26:46 CET

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.