From dev-return-39667-archive-asf-public=cust-asf.ponee.io@subversion.apache.org Wed Oct 23 02:18:42 2019 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 DA28418062C for ; Wed, 23 Oct 2019 04:18:41 +0200 (CEST) Received: (qmail 51358 invoked by uid 500); 23 Oct 2019 02:18:40 -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 51123 invoked by uid 99); 23 Oct 2019 02:18:39 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Oct 2019 02:18:39 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 11DCB1A32B4 for ; Wed, 23 Oct 2019 02:18:39 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.749 X-Spam-Level: X-Spam-Status: No, score=0.749 tagged_above=-999 required=6.31 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.25, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-he-de.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id b5LulyZk6rj3 for ; Wed, 23 Oct 2019 02:18:37 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.222.193; helo=mail-qk1-f193.google.com; envelope-from=vega.james@gmail.com; receiver= Received: from mail-qk1-f193.google.com (mail-qk1-f193.google.com [209.85.222.193]) by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with ESMTPS id E4E3C7DDE5 for ; Wed, 23 Oct 2019 02:18:36 +0000 (UTC) Received: by mail-qk1-f193.google.com with SMTP id u184so18402467qkd.4 for ; Tue, 22 Oct 2019 19:18:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:resent-from:resent-date:resent-message-id :resent-to:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=ouEFO06i1kzuwCj6fUC45RI/4bmClESVwJR6wIcl2yc=; b=h3jivA2tyY5oyx0HM11CpwPu7k5REwNYzIyV4qEjWyOF7QAFwIgAhujUYnCGkFp3RQ b6pR8whkjSJodFIObC/t7SdYxycpx+SRSfIDCXHp287xA9Efuttv4Lz8qBPPGlUWoS63 f5xWEeMaF9iUs1Waj0rBe0NqSMmhmH6LuWRttXLkNOIl5ZrYVpcfBCzu+i/x/zGqxgPq /zoah5zza566BIU03/H8vfnxcGKq2ARV+/3giYR/E8YNBwsevRpxZthMsWVumDe/lZMG HP08pgekYk6isjhODmQRR/8bokVw23SP0h5yjIKx4C0UsomfgyPBMIpuEPCliJ+EgF3K CW/w== X-Gm-Message-State: APjAAAUh9F7ygzGBPHmKYTpPJv72d22LNkq3TH2Ysfh/M4/GmQISP9mm /jhXk05EB4jqYRchuyACGaS50vcw X-Google-Smtp-Source: APXvYqz4jPbPvXRXesbEs/gCc+CNQZYYiW/ZZci1gPq2GohJ8oRT6lR4c1F7V83aimiccIgEUZEECw== X-Received: by 2002:a37:bc86:: with SMTP id m128mr6461886qkf.161.1571797109558; Tue, 22 Oct 2019 19:18:29 -0700 (PDT) Received: from odin (pool-108-49-100-227.bstnma.fios.verizon.net. [108.49.100.227]) by smtp.gmail.com with ESMTPSA id r36sm8973521qta.27.2019.10.22.19.18.29 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 22 Oct 2019 19:18:29 -0700 (PDT) Received: from jamessan by odin with local (Exim 4.92.3) (envelope-from ) id 1iN6EG-0001NS-Pt for dev@subversion.apache.org; Tue, 22 Oct 2019 22:18:28 -0400 Resent-From: James McCoy Resent-Date: Tue, 22 Oct 2019 22:18:28 -0400 Resent-Message-ID: <20191023021828.oqw2gcysddmcgq5h@localhost> Resent-To: dev@subversion.apache.org Date: Tue, 22 Oct 2019 19:07:56 -0400 From: James McCoy To: dev@subversion.apache.org Subject: Re: 1.13.x and swig-py3 Message-ID: <20191022230756.x2sd7w4fdxld23ud@localhost> Mail-Followup-To: dev@subversion.apache.org References: <3ae4cbf6-d2b6-0f11-0f5a-6be832a44966@poem.co.jp> <20191018232255.uao4rugqzw5nr25s@tarpaulin.shahaf.local2> <3553d1eb-e712-7f06-613a-5a9cd9b45f8a@apache.org> <96108c08-d507-661d-6385-8ffc46a36df1@apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20180716 On Mon, Oct 21, 2019 at 01:35:45PM +0200, Branko Čibej wrote: > On 21.10.2019 13:16, Julian Foad wrote: > > Johan Corveleyn wrote: > >> Nathan Hartman wrote: > >>     Branko Čibej  wrote: > >>      > By the principle of least surprise, I think it > >>      > would be better to merge to trunk, create a > >>      > new 1.13.0 release candidate > >> > >>     +1 > >> > >>      > and (maybe?) restart the soak. > >> > >>     I support this idea even if the soak must restart or be extended. > >> > >> +1. Since 1.13 contains so very little, I think it's good to be a bit > >> flexible with our planned timing here, to get this on board. I.e. > >> let's merge it in, cut a new rc, and restart the soak. > > > > Dear all, with respect, > > > > I would love to see the Py3 support released ASAP. > > > > But, have we not learned from our past mistakes?  We have prepared a > > regular release that is right now looking to be ready to deploy next > > week, on time.  If we postpone and destabilize it now [1], this would > > make mockery of "regular" releases.  I would love to trust that > > merging the branch will go smoothly with no follow-up required and no > > extra time taken, but history has taught us that it is foolish to > > assume so. > > > > Surely the right approach is to release what we have got (the > > currently soaking 1.13), then release the new one as soon as we can > > get it ready. It sounds like it's not suitable for a patch release, so > > we'll make it a new minor release, calling it 1.14. > > > If you (or some other RM volunteer) is prepared to roll 1.14 with Python > 3 support in, say, a month after 1.13 -- with all that implies for > downstream packagers -- then sure. FWIW, since we switched to the new release model, I (in my capacity as packager for Debian) basically ignore non-LTS releases. It's easier to ignore them, since I know I only want an LTS release in Debian's release, and would rather not risk getting "stuck" with a non-LTS release when Debian freezes. The downside to this is that the non-LTS releases don't get any of the feedback of going through the various builds/tests on Debian's infrastructure. I'll likely make an exception for the Python 3 support since there's a significant push within Debian to switch over to Python 3 ASAP, and definitely in time for the next release. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB