From dev-return-40253-archive-asf-public=cust-asf.ponee.io@subversion.apache.org Fri Feb 14 12:37:03 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id A2C6D180661 for ; Fri, 14 Feb 2020 13:37:02 +0100 (CET) Received: (qmail 14805 invoked by uid 500); 14 Feb 2020 12:37:02 -0000 Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@subversion.apache.org Received: (qmail 14764 invoked by uid 99); 14 Feb 2020 12:37:01 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Feb 2020 12:37:01 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 0E080181253 for ; Fri, 14 Feb 2020 12:37:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.501 X-Spam-Level: X-Spam-Status: No, score=0.501 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.2, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-he-de.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id hfKEpZOCFcVv for ; Fri, 14 Feb 2020 12:36:56 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2607:f8b0:4864:20::230; helo=mail-oi1-x230.google.com; envelope-from=hartman.nathan@gmail.com; receiver= Received: from mail-oi1-x230.google.com (mail-oi1-x230.google.com [IPv6:2607:f8b0:4864:20::230]) by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with ESMTPS id 33A417E135 for ; Fri, 14 Feb 2020 12:36:56 +0000 (UTC) Received: by mail-oi1-x230.google.com with SMTP id b18so9284077oie.2 for ; Fri, 14 Feb 2020 04:36:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=c99j3wVIm/5BPfvdtjVC47wigxXRIuFVkCp5rD04EfY=; b=H9iI3nFDPU/iRAiLwVw2LQvFPXlS7MkVqUGOm8kwxi+iN05m8XUzsyq8l7nB8Y1uDb rTwcw5LLuANMj2uwk86/CSpCpjRXR/+nUSfM6sLgWemhtAm17PqUmAw+IDWPxI0Qwr/5 tSfwsbxPCMSKTPVMYuO6gU47ShBnA+82Fgg4f83YO7/fnJCYlVVX5+3tzyZ2bE8JSbe6 tcG6F0DCefqZmgMoS50WMnhYaFm7ymNt+TJvCPEoVlMJ8Rysz8MbBdR8YWrjQTaA7x79 Y3IfzP1QkeV8pHu9f5q6+MoA+/3Z3rray15ARnnBeP9ET84NOp+ipoF8D3QZ0HR6zbZM j3zQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=c99j3wVIm/5BPfvdtjVC47wigxXRIuFVkCp5rD04EfY=; b=FXmZ48nkmNZeO3sVYA1gE/uLN2mm9MLfmo3gj6Wzp+0d3MtTzR0751cmOo20twV9zY 5dUmyNCMhOGA6TrTt3dZHiijYONux10GSCLf5H+AFy2uei3c6h87s7lLMpom/63jsWjv CLPdZGp04v7hZ65Sox/cd8hVbPXCZhJmGw+JKtxPZccZO6YB/vAa0/HeEAYpbOMA3JBF cD6Md5ces95QjD0pggHiQypVZ3g+1Thm9kqCXEzjiElT+/sb9MQXFM+2vaKVy4YWNx9y EXkQlPTgsoD1AXDjEc2S5kOr8bgwBukm30qQgf+uIkM9zze+rSM7uCH42/pOAK20PXCK zfBw== X-Gm-Message-State: APjAAAWtmr6h9WCp/rvVzLrhgJVCaCfVUNS46U8dPul5hpA25TMxgf5k 3/MVse88a1zgtOTdYZJEYy9pe89XI0HQgK1OEew= X-Google-Smtp-Source: APXvYqzne4/r3DugiBFn1EUOrrqEbRJIOsVHirMbrAfPQ9T0r2cF8+Wz2GEiT2pWly6EcE3VOqu3/Ciu/YEwOlHFXzI= X-Received: by 2002:aca:4996:: with SMTP id w144mr1617476oia.111.1581683814799; Fri, 14 Feb 2020 04:36:54 -0800 (PST) MIME-Version: 1.0 References: <75ecd9d6-2ac3-1326-23b4-7dc99cbfb075@apache.org> <20200124112219.GB38254@ted.stsp.name> <20200214122627.GU47683@ted.stsp.name> In-Reply-To: <20200214122627.GU47683@ted.stsp.name> From: Nathan Hartman Date: Fri, 14 Feb 2020 07:36:43 -0500 Message-ID: Subject: Re: Release Management, Subversion 1.14 To: Julian Foad , dev@subversion.apache.org Content-Type: multipart/alternative; boundary="000000000000ed9d5e059e887543" --000000000000ed9d5e059e887543 Content-Type: text/plain; charset="UTF-8" On Fri, Feb 14, 2020 at 7:26 AM Stefan Sperling 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. Nathan --000000000000ed9d5e059e887543 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Feb 14, 2020 at 7:26 AM Stefan Sperling <stsp@elego.de> wrote:
- Release notes and CHANGES need to be updated.
=C2=A0 There are relatively few changes since we only have to document what=
=C2=A0 changed since September. I am wondering if 1.14 release note should<= br> =C2=A0 summarize what occurred betwen 1.10 and 1.14, or if they should be =C2=A0 written relative to 1.13 as the current draft implies.
=C2=A0 For users upgrading from LTS to LTS it might make sense to give an =C2=A0 overview of what changed on one page. And it would also give us more=
=C2=A0 material to fill the release notes page with :)

I was thinking a= bout this a few days ago. I think that LTS releases are a different "l= ine" and the release notes should include changes since 1.10. If the c= ommunity 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<= br> =C2=A0 new plan agreed upon. If we don't decide on anything we'll e= nd up with a
=C2=A0 1.15 release planned for October 2020. I doubt this plan is still vi= able
=C2=A0 given how little is happening right now in order to prepare 1.14.
I think that the minor version n= umber should not be incremented unless there are new features. If only bug = fixes are available, the policy should be to backport them to the maintaine= d 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 regul= ar release schedule.

Nat= han



--000000000000ed9d5e059e887543--