[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: Nathan Hartman <hartman.nathan_at_gmail.com>
Date: Fri, 14 Feb 2020 07:36:43 -0500

On Fri, Feb 14, 2020 at 7:26 AM Stefan Sperling <stsp_at_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.

More below...

- 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.
I think that the minor version number should not be incremented unless
there are new features. If only bug fixes are available, the policy should
be to backport them to the maintained releases and release a new point
version every 6 months. So 1.14.x could be the latest version for some
time, but we'll continue to have a regular release schedule.

Received on 2020-02-14 13:37:02 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.