From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.devel Subject: Re: Next release from master Date: Mon, 18 Jan 2016 10:06:14 +0100 Message-ID: <87lh7n1cl5.fsf@gmx.de> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1453108005 9075 80.91.229.3 (18 Jan 2016 09:06:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 18 Jan 2016 09:06:45 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 18 10:06:35 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aL5lg-0001bM-BD for ged-emacs-devel@m.gmane.org; Mon, 18 Jan 2016 10:06:32 +0100 Original-Received: from localhost ([::1]:58359 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aL5la-0008WD-0H for ged-emacs-devel@m.gmane.org; Mon, 18 Jan 2016 04:06:26 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38709) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aL5lW-0008W2-IG for emacs-devel@gnu.org; Mon, 18 Jan 2016 04:06:23 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aL5lS-0008Me-Hi for emacs-devel@gnu.org; Mon, 18 Jan 2016 04:06:22 -0500 Original-Received: from mout.gmx.net ([212.227.17.21]:60999) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aL5lS-0008Ma-8c for emacs-devel@gnu.org; Mon, 18 Jan 2016 04:06:18 -0500 Original-Received: from detlef.gmx.de ([87.146.48.239]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0LaXmV-1Zs2Y31JE7-00mKDB for ; Mon, 18 Jan 2016 10:06:16 +0100 In-Reply-To: (John Wiegley's message of "Sun, 17 Jan 2016 15:10:13 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) X-Provags-ID: V03:K0:GXaK/5rKfA41dfeQjDx2mfCVrvxA5jFhSNTR0t8wvoU1oIxuClg dJxdmRRwlooI7+Aca0otytBp6OBDIHMbqZq+UA84E75PCZbErIWC1WZ7AwKPgv5xzzXlDfg pDS3jVS+9GLXWgWCooccGG0llE1KiYElVG2ZiL9rh1Wb8pX7Xu88Y12Cg7O+u84HDgzmVD/ YMTNCTEL4NJd/J+84dOBQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:Qg/BIXPQBus=:gf7lQ9pMFxUGKpiuo+NzLD R3bkm4VDjiWEP7nFhMq/0UsvbMbzE5Dn3q+PLjGN07LFF0uxoz7/meyDf0/tVkLl+BIStcGaR krcWhzyMSqddYX+stcHu/em7+pl5cDlmM0jFe7Iys5ALQDh5lM2/ItST3e8UCQmeJKfdoBCHN kR/W26TDjRaI9qIwqUcrc3e/k0fn5znIHaYUT3u7YdsbH8y6iNH8vA6lBMJp9N2YLBHgCJ59v nCKLF/iMtH7gOAhUyLWQFUPvY1loj/lZaviWq/JZQjvTlMnhUrbQSr14tb5Is0o7eSGtY0xH7 M3OoVQNoHectk7uTJjIYJ3JOcuYVPYfx1xO/sVTkmN16SGXpZtfZfOuoUHODGbZT6+OdtVgir uH2IsGztZw/6F5Tx+s2EFbPO2lfran+9Wgdygd9gCd0PVK6f9khis27TQZPE+NcBqbWZXJlks 9UazH2hssPECLPWxV/FKyKS/99e4gjHUiea49kGMUgwX5/eNEZDAuH1juUwUgN8hbO36FlJk/ zNjpedhYhRWTxIDM/e5ttNhHZQ7WZlE6EU5ZJgecsCVuEVoyjADHwVaGGOU5AeSt4hD2Wxmv2 EznfHLrFHXBacyVv7dKf3Ck3KISiBfsfVE7PndOLts1cPkE5MJLMouwHlJEWGt+uABn76mtIx 6Ml2Hv+EaEth4+d7k5Ej/4biDm0Mkekp7UgjG05sQm+qQErrlgJ8hxVyvK1pwtGrTUDKonMy0 fSysxWcL8ku6lwWm7G8CYXBPtSLybdwtYvsnGYRjRuU1ndpETyq+BFRLVhcPqAMg2nzJcqsT X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 212.227.17.21 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:198240 Archived-At: John Wiegley writes: >> My own conclusion based on how things worked during Emacs-24.N was that >> we're better off incrementing the major version every time there are new >> features. IOW the next release form master should be called 26.1 and 25.N >> should be kept for a bugfix-only releases from the emacs-25 branch. > > I think you have a good point, Stefan. master should become emacs-26 at some > point in the future, once it's ready, while emacs-25 should only continue to > improve and stabilize the 25.x series. > > I imagine we will be actively working in emacs-25 for at least 25.1 and 25.2, > before shifting attention over to master and leaving emacs-25 only for > maintenance. What release cycles are we're speaking about, in terms of time? Example: I have committed the first bits to the master branch of what would be Tramp 2.3. Incompatible (the code, NOT the external interface) to Tramp 2.2.13 in Emacs 25.1. If it takes a long time until Emacs 26 is released, that code should go to Emacs 25.2, somehow. Best regards, Michael.