From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.devel Subject: Re: Feature freezes and Emacs 25 Date: Sat, 14 Nov 2015 21:42:47 -0500 Message-ID: References: <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; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1447656885 9430 80.91.229.3 (16 Nov 2015 06:54:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 16 Nov 2015 06:54:45 +0000 (UTC) Cc: Eli Zaretskii , nicolas@petton.fr, Emacs-devel To: Xue Fuqiao Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 16 07:54:44 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 1ZyDgZ-0008FJ-PP for ged-emacs-devel@m.gmane.org; Mon, 16 Nov 2015 07:54:43 +0100 Original-Received: from localhost ([::1]:46037 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZyDgZ-0004l9-Cj for ged-emacs-devel@m.gmane.org; Mon, 16 Nov 2015 01:54:43 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47945) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxnHH-0006Jv-61 for emacs-devel@gnu.org; Sat, 14 Nov 2015 21:42:51 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZxnHG-0007DQ-C3 for emacs-devel@gnu.org; Sat, 14 Nov 2015 21:42:51 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:35834) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxnHE-0007D9-SN; Sat, 14 Nov 2015 21:42:48 -0500 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1ZxnHE-0007pW-AS; Sat, 14 Nov 2015 21:42:48 -0500 X-Spook: Gulf Cartel Exon Shell H5N1 Legion of Doom Power quiche X-Ran: Zq(36Q2PMRz}&d=e:oa>Y$}vNw\t;I4ZXuRQfOR;yGiH%7Wk8LIfk6}k>]^':ZS=+OV[aw X-Hue: green X-Attribution: GM In-Reply-To: (Xue Fuqiao's message of "Thu, 12 Nov 2015 16:53:17 +0800") User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). 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:194513 Archived-At: Xue Fuqiao wrote: > Hmm... Personally, I think "for release" is just a list of activities > that must be completed before the next release, but "release process" or > "release cycle" is throughout Emacs development.=20 Fair enough. >> No one else has shown any interest in tracking such things AFAIK. > > Perhaps many developers aren't aware of it. (I'm an example.) AFAIK, nobody thought to even ask "how shall we track the bugs we need to fix for the next release". Till now! :) > Well, I mean _build and upload_ the binary. Maybe Someone=E2=84=A2 famil= iar > with Windows should write a script to build a Windows binary for release > automatically. Perhaps. Personally I wouldn't like to see "provide pre-built binaries for MS Windows users" becomes an "official" responsibility of Emacs. It's just something that some people have been doing on a best effort basis. But of course the people who do the work get to make the decisions.