From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Wiegley Newsgroups: gmane.emacs.devel Subject: Re: Feature freezes and Emacs 25 Date: Mon, 09 Nov 2015 13:55:08 -0800 Message-ID: References: <56259FDD.8040401@dancol.org> <87zizeme8k.fsf@tromey.com> <5625B166.3080104@dancol.org> <86zizdczhp.fsf@stephe-leake.org> <871tc315y3.fsf@lifelogs.com> <83k2pvqg0l.fsf@gnu.org> <837fluqkd1.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1447106207 22059 80.91.229.3 (9 Nov 2015 21:56:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 9 Nov 2015 21:56:47 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 09 22:56:31 2015 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 1ZvuQR-0004R1-2P for ged-emacs-devel@m.gmane.org; Mon, 09 Nov 2015 22:56:31 +0100 Original-Received: from localhost ([::1]:55839 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvuQQ-0005Eq-CS for ged-emacs-devel@m.gmane.org; Mon, 09 Nov 2015 16:56:30 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40329) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvuPm-0004i9-2G for emacs-devel@gnu.org; Mon, 09 Nov 2015 16:55:50 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZvuPl-0000sK-5w for emacs-devel@gnu.org; Mon, 09 Nov 2015 16:55:49 -0500 Original-Received: from mail-pa0-x22c.google.com ([2607:f8b0:400e:c03::22c]:35489) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvuPg-0000q5-He; Mon, 09 Nov 2015 16:55:44 -0500 Original-Received: by pasz6 with SMTP id z6so217900977pas.2; Mon, 09 Nov 2015 13:55:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:in-reply-to:date:message-id:references :user-agent:mail-followup-to:mime-version:content-type; bh=2qWagn3OFizptRFAaXfaJr2KEtw76OP7POzvsOUIwWM=; b=SzA1xJHO17IL/W11xYw1VpOduU7xItx4LvCswQ2X51GvZLfNV7xQAj5zZDMWfnN4X7 JPFqYqU5VQLaft9mDDBH30rRZ5Q3B0KYoad7TpsoOy0zXJreiIL6yMgTSbOAS/hJHXBH 7d8bImojieYm5d2TDc+SLAcmajcnfoPD1mBLjXOhuJuwGA0mFyRVIX8hk04MXX2HeyPF aRRzb2XyHzV194APt1dgz3QpidJkklShifbMEan1nhsfIwvhbmCYlq+OrdWIceFS2K/t 6BR+ID49xoUAyHOxbTKoXQmrz2Adzo3kJT7U+mbGwtQM33MA6Cr561zcTVi0cSpoMeKT pWjw== X-Received: by 10.68.201.73 with SMTP id jy9mr256640pbc.102.1447106143819; Mon, 09 Nov 2015 13:55:43 -0800 (PST) Original-Received: from Vulcan.attlocal.net (76-234-68-79.lightspeed.frokca.sbcglobal.net. [76.234.68.79]) by smtp.gmail.com with ESMTPSA id fk8sm49685pab.33.2015.11.09.13.55.41 (version=TLS1 cipher=AES128-SHA bits=128/128); Mon, 09 Nov 2015 13:55:41 -0800 (PST) X-Google-Original-From: "John Wiegley" Original-Received: by Vulcan.attlocal.net (Postfix, from userid 501) id 1F136104A5501; Mon, 9 Nov 2015 13:55:41 -0800 (PST) In-Reply-To: <837fluqkd1.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 07 Nov 2015 10:33:46 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin) Mail-Followup-To: Eli Zaretskii , emacs-devel@gnu.org X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::22c 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:193769 Archived-At: >>>>> Eli Zaretskii writes: > I think we should first decide whether new features that are "almost ready" > should or should not be in 25.1. Two examples that immediately come to mind > are dynamic loading and xwidgets; I don't know if there are others. After we > make the decision, we could see if one week's time is enough. I'd like to see both of those in 25.1. Let's freeze this Friday, and take a step back. We have several courses open: 1. Decide that what we have now should become 24.6. 2. Decide it will become 25.1. 3. Decide that we want to bring in more features that aren't yet complete, and so push the freeze to a future date. > We used to cut a release branch fairly early in the pretest , certainly at > least when the first pretest tarball is put on alpha.gnu.org. Does the above > mean you want the pretest to be worked on on master instead? I'd actually like to know more about our current release flow, before having that discussion here. I don't know yet what I want in that respect. John