From dev-return-39629-archive-asf-public=cust-asf.ponee.io@subversion.apache.org Fri Oct 18 23:23:05 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 DD3501804BB for ; Sat, 19 Oct 2019 01:23:04 +0200 (CEST) Received: (qmail 64216 invoked by uid 500); 18 Oct 2019 23:23:04 -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 64196 invoked by uid 99); 18 Oct 2019 23:23:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Oct 2019 23:23:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 0DB16C0AFF for ; Fri, 18 Oct 2019 23:23:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.799 X-Spam-Level: X-Spam-Status: No, score=-0.799 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=daniel.shahaf.name header.b=H6e9Rte1; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=PGl5nMAY Received: from mx1-he-de.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Kswvc_IGUxWs for ; Fri, 18 Oct 2019 23:23:00 +0000 (UTC) Received-SPF: Pass (helo) identity=helo; client-ip=64.147.123.21; helo=wout5-smtp.messagingengine.com; envelope-from=d.s@daniel.shahaf.name; receiver= Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with ESMTPS id D54B97DDBE for ; Fri, 18 Oct 2019 23:22:59 +0000 (UTC) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 1E6F74E8; Fri, 18 Oct 2019 19:22:58 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 18 Oct 2019 19:22:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= daniel.shahaf.name; h=date:from:to:subject:message-id:references :mime-version:content-type:in-reply-to; s=fm1; bh=Eu7GnsrbEsLbN1 mfpreGJZ9fP/w/R4lQN2UbjYcHaWo=; b=H6e9Rte1npjxbglYiFmCZFlaYr08+4 X3hfDDGaOMnugf8v7iVPBjXdif7L2PXKQl6YT172J45uSaFhuCSm5MeyYJBKIqeW ps2ra55wWKCV/4efpDAv3LxCWPqVNPaulYEor4Td6k2bLbHX1AN9fYTBjslJvL5w 3l4f7K0IDX+ruEnuLYeYO7wr92igAoo6yTwcDJD8NZ3iU22b09yPs4pFVWsqlv1a 0CxtT/tFrAAlb/RmoJpZduPwJuDXvIz06Jycavk1l/2lL9vnrAwDkw/qOAJoAMrQ dXiGA2LC0xtPNgjmoZrXVNqdE8wP3h8wsIBM8yKgzboP54wUXjmkeOVQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=Eu7Gns rbEsLbN1mfpreGJZ9fP/w/R4lQN2UbjYcHaWo=; b=PGl5nMAYA3mD58gCwQdQZE M+TUChwU59FoyURWmYCY6DdhBl09EqU1E+Vu+pM8V2Do7wV0L9vlR/mJ4fq5x3uo DE9o8SdluNR9fvDmfHSkwK6RSJt5drDPaC9yjkzuDxTAJdLf8UdpGrA2u1+bBkMx qEH9C5i3ZAXux0fH/fVuFHDREds95w/rA0EE/DnGZ6negMixM9glnFNMQyC5RwVD vz5q6aW9uAlWlvRvR2I04FMFiDqa73F3R736LcYoAHaAMLDkvK1UQ/liCdhpu3+Z U9tMOIwVMXVY1cmAdqWDTgaaYkhRqhggv3Wv6LcbE3BzVvdR9qrB/gCHHeO0fmJg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrkedtgddvudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtuggjfgesthdttd dttdervdenucfhrhhomhepffgrnhhivghlucfuhhgrhhgrfhcuoegurdhssegurghnihgv lhdrshhhrghhrghfrdhnrghmvgeqnecukfhppeejledrudektddrheejrdduudelnecurf grrhgrmhepmhgrihhlfhhrohhmpegurdhssegurghnihgvlhdrshhhrghhrghfrdhnrghm vgenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from tarpaulin.shahaf.local2 (bzq-79-180-57-119.red.bezeqint.net [79.180.57.119]) by mail.messagingengine.com (Postfix) with ESMTPA id 18D6C80059 for ; Fri, 18 Oct 2019 19:22:57 -0400 (EDT) Received: by tarpaulin.shahaf.local2 (Postfix, from userid 1005) id 46w2Bl3DhJzSV; Fri, 18 Oct 2019 23:22:55 +0000 (UTC) Date: Fri, 18 Oct 2019 23:22:55 +0000 From: Daniel Shahaf To: dev@subversion.apache.org Subject: 1.13.x and swig-py3 (was: Re: Test failures with Python 3 (Re: PMCs: any Hackathon requests? (deadline 11 October))) Message-ID: <20191018232255.uao4rugqzw5nr25s@tarpaulin.shahaf.local2> References: <7fb80cbe-62a6-23e5-ad19-c6b09a7f5c3f@poem.co.jp> <45c1b6f1-d392-9a2c-7f2c-0bea80a4d6aa@poem.co.jp> <20191016013628.ewqtcfcfoyy3ygcd@tarpaulin.shahaf.local2> <2b7da5e3-0be4-04fc-37ad-e332154b84df@poem.co.jp> <6d63d1ff-bc47-4d89-98b2-1da6e4a5590c@www.fastmail.com> <3ae4cbf6-d2b6-0f11-0f5a-6be832a44966@poem.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Yasuhito FUTATSUKI wrote on Fri, Oct 18, 2019 at 23:09:19 +0900: > On 2019/10/16 21:12, Johan Corveleyn wrote: > > This makes me wonder: should that be fixed specifically on trunk, and > > nominated for backport to 1.13, so we can possibly claim basic support > > for Python 3 in our build and test processes (in at least one released > > version) before the end of this year? > > > > Or should we reintegrate the swig-py3 branch ASAP, and nominate *that* > > for backport to 1.13, so we can have Python 3 support, including swig > > bindings? > > I prefer the latter, as one of users :) I want to use > tools/hook-scripts/mailer/mailer.py with Python 3. If we want this to happen, we should first of all complete the swig-py3 branch and merge it to trunk. What's not clear to me is what would happen afterwards. Is anyone proposing to delay 1.13.0 until swig-py3 is merged (remember that we are already more than halfway through the soak)? If not, how would merging swig-py3 to 1.13.x coexist with the premise of "no destabilizing changes in patch releases"? Would we have to delay merging swig-py3 to 1.13.x until January, when py2 has finally gone out of support? What should we do about swig-py3 support in 1.12.x and 1.10.x, which are both LTS? Should we say anything about swig-py2 / swig-py3 in the release notes _today_, before 1.13.0 has been released, about our plans for 1.13.x patch releases?