From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Next release from master Date: Mon, 18 Jan 2016 17:55:11 +0200 Message-ID: <83a8o2evc0.fsf@gnu.org> References: Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1453132556 24067 80.91.229.3 (18 Jan 2016 15:55:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 18 Jan 2016 15:55:56 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: John Wiegley Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 18 16:55:48 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 1aLC9j-0006Ll-Uv for ged-emacs-devel@m.gmane.org; Mon, 18 Jan 2016 16:55:48 +0100 Original-Received: from localhost ([::1]:60430 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLC9g-0007xY-C8 for ged-emacs-devel@m.gmane.org; Mon, 18 Jan 2016 10:55:44 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58101) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLC99-00074g-IB for emacs-devel@gnu.org; Mon, 18 Jan 2016 10:55:12 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aLC96-0002j6-C3 for emacs-devel@gnu.org; Mon, 18 Jan 2016 10:55:11 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:32792) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLC94-0002ig-RB; Mon, 18 Jan 2016 10:55:06 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1243 helo=HOME-C4E4A596F7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aLC93-00019b-5J; Mon, 18 Jan 2016 10:55:06 -0500 In-reply-to: (message from John Wiegley on Sun, 17 Jan 2016 15:10:13 -0800) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:198256 Archived-At: > From: John Wiegley > Date: Sun, 17 Jan 2016 15:10:13 -0800 > Cc: emacs-devel@gnu.org > > > 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. Are you changing your mind? ;-) You told me something different in http://lists.gnu.org/archive/html/emacs-devel/2015-11/msg01372.html. > 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. You seem to be talking about something that never happened before in Emacs: we never left any branch "for maintenance", we left it for good. Once the decision was made that the next release will be from master, the branch was abandoned, and never revisited except in emergency (e.g., if some super-critical bug was reported in the last release that required an urgent fix).