From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id ffcb6ac1 for ; Sun, 16 Feb 2020 11:15:53 +0000 (UTC) Received: (qmail 3475 invoked by alias); 16 Feb 2020 11:15:48 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 45441 Received: (qmail 2319 invoked by uid 1010); 16 Feb 2020 11:15:48 -0000 X-Qmail-Scanner-Diagnostics: from wout1-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.1/25718. spamassassin: 3.4.2. Clear:RC:0(64.147.123.24):SA:0(-2.6/5.0):. Processed in 0.716124 secs); 16 Feb 2020 11:15:48 -0000 X-Envelope-From: d.s@daniel.shahaf.name X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at daniel.shahaf.name does not designate permitted sender hosts) X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrjeeggddviecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukffogggtgfesthejtddtre dtvdenucfhrhhomhepffgrnhhivghlucfuhhgrhhgrfhcuoegurdhssegurghnihgvlhdr shhhrghhrghfrdhnrghmvgeqnecukfhppeejledrudejkedrjedrudekleenucevlhhush htvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegurdhssegurghnihgv lhdrshhhrghhrghfrdhnrghmvg X-ME-Proxy: Date: Sun, 16 Feb 2020 11:15:11 +0000 From: Daniel Shahaf To: zsh-workers@zsh.org Subject: Plan for the 5.9 branch Message-ID: <20200216111511.73ea28fa@tarpaulin.shahaf.local2> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit A few weeks ago I created a 5.9 branch for bugfixes/patches that seemed too risky to push to master during pre-release stabilization. I'd like to merge that branch to master in a few weeks, when it's clear there won't be a 5.8.1 for regressions. (Alternatively, we could merge the branch now; that won't block us from creating a 5.8.1 regression-fixing release with or without the changes from the 5.9 branch.) --- As to branching policy, in the future we should probably do things the other way around; that is: in the run-up to the 5.9 release next year, rather than stabilize on master and open a 5.10 branch for destabilizing changes, we should open a 5.9 branch for stabilization and leave master open to destabilizing changes. (Fortunately, due to how git fast-forward merges work, the current 5.9 branch won't interfere with this plan.) Makes sense? Cheers, Daniel