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: Sun, 24 Jan 2016 20:35:29 +0200 Message-ID: <83twm23jwu.fsf@gnu.org> References: <8qegda3kfg.fsf@fencepost.gnu.org> <56A185D8.9030807@yandex.ru> <56A18A70.2060409@yandex.ru> <83powu6pdg.fsf@gnu.org> <83lh7f3w4c.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1453660529 782 80.91.229.3 (24 Jan 2016 18:35:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 24 Jan 2016 18:35:29 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 24 19:35:29 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 1aNPVX-0007Wf-G0 for ged-emacs-devel@m.gmane.org; Sun, 24 Jan 2016 19:35:27 +0100 Original-Received: from localhost ([::1]:33066 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNPVW-0006ws-Ju for ged-emacs-devel@m.gmane.org; Sun, 24 Jan 2016 13:35:26 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57625) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNPVH-0006wd-Nx for emacs-devel@gnu.org; Sun, 24 Jan 2016 13:35:12 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aNPVD-0000lx-NG for emacs-devel@gnu.org; Sun, 24 Jan 2016 13:35:11 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:46359) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNPVD-0000lt-KV; Sun, 24 Jan 2016 13:35:07 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4228 helo=HOME-C4E4A596F7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aNPVC-000527-TI; Sun, 24 Jan 2016 13:35:07 -0500 In-reply-to: (message from Stefan Monnier on Sun, 24 Jan 2016 13:04:40 -0500) 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:198719 Archived-At: > From: Stefan Monnier > Cc: emacs-devel@gnu.org > Date: Sun, 24 Jan 2016 13:04:40 -0500 > > the place where to put bug fixes should always be the same (and same > for new features). That's impossible. Every development means bugs, so bugfixes will happen on all active branches. Some of them will be different, some identical. But all of the branches will get bugfixes. And the same for new features. > > (Also, I think "stable bleeding-edge" is self-contradictory.) > > Yes, it is, but that's what we want people to use for things like > `emacs-snapshot': when we're in feature freeze, they should use the > "bug-fix branch", and when we're not they should use the "new > features" branch. With 3 branches, there's no need for feature freeze, so I don't think I understand how all this is relevant to the issue at hand. Also, didn't you just say that "stable bleeding-edge" should always be the same branch? But here you seem to be saying that it's sometimes this and sometimes that.