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: Fri, 22 Jan 2016 09:32:27 +0200 Message-ID: <83powu6pdg.fsf@gnu.org> References: <8qegda3kfg.fsf@fencepost.gnu.org> <56A185D8.9030807@yandex.ru> <56A18A70.2060409@yandex.ru> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1453447942 12354 80.91.229.3 (22 Jan 2016 07:32:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 22 Jan 2016 07:32:22 +0000 (UTC) Cc: emacs-devel@gnu.org, dgutov@yandex.ru To: "John Wiegley" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 22 08:32:20 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 1aMWCh-0005Qx-Fm for ged-emacs-devel@m.gmane.org; Fri, 22 Jan 2016 08:32:19 +0100 Original-Received: from localhost ([::1]:51126 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMWCg-0003pC-RM for ged-emacs-devel@m.gmane.org; Fri, 22 Jan 2016 02:32:18 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43981) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMWCd-0003p5-Fz for emacs-devel@gnu.org; Fri, 22 Jan 2016 02:32:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aMWCc-0004bY-L5 for emacs-devel@gnu.org; Fri, 22 Jan 2016 02:32:15 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:33338) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aMWCY-0004b9-TZ; Fri, 22 Jan 2016 02:32:10 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4839 helo=HOME-C4E4A596F7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aMWCY-0007fn-55; Fri, 22 Jan 2016 02:32:10 -0500 In-reply-to: (message from John Wiegley on Thu, 21 Jan 2016 17:56:03 -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:198558 Archived-At: > From: John Wiegley > Cc: emacs-devel@gnu.org, Eli Zaretskii > Date: Thu, 21 Jan 2016 17:56:03 -0800 > > >>>>> Dmitry Gutov writes: > > >> Or are you saying that once we've frozen for X.1, any and all > >> changes to be included in X are allowed, since they should all be stabilizing > >> changes? > > > More or less, yes. No breaking changes in 25.2. > > What do you think, Eli? Should master become 26.1? If we decide that emacs-25 will only be used for fixing bugs, i.e. all 25.x releases after 25.1 will be bugfix releases, then yes, I think master should become 26.1. > What would this mean for the likelihood of 25.2? It would mean 25.2, 25.3, etc. will fix bugs and generally add nothing new. It might also mean the release cycle on the emacs-25 branch could be very fast (beyond 25.1), with just a small number of pretests before the actual release. We never tried to stick to this principle, though, except with Emacs 24.5.