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: Release-critical bugs Date: Fri, 19 Sep 2014 20:34:29 +0300 Message-ID: <83sijnzf8a.fsf@gnu.org> References: <87mw9yb2f8.fsf@engster.org> <83bnqd3b5n.fsf@gnu.org> <83mw9w25ei.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1411148123 9089 80.91.229.3 (19 Sep 2014 17:35:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 19 Sep 2014 17:35:23 +0000 (UTC) Cc: emacs-devel@gnu.org To: Glenn Morris Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Sep 19 19:35:15 2014 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 1XV25Q-0002vh-21 for ged-emacs-devel@m.gmane.org; Fri, 19 Sep 2014 19:35:12 +0200 Original-Received: from localhost ([::1]:59657 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XV25P-00050l-NE for ged-emacs-devel@m.gmane.org; Fri, 19 Sep 2014 13:35:11 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52645) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XV256-00050e-Vs for emacs-devel@gnu.org; Fri, 19 Sep 2014 13:34:59 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XV250-0000VM-9p for emacs-devel@gnu.org; Fri, 19 Sep 2014 13:34:52 -0400 Original-Received: from mtaout29.012.net.il ([80.179.55.185]:35694) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XV250-0000Ur-2B; Fri, 19 Sep 2014 13:34:46 -0400 Original-Received: from conversion-daemon.mtaout29.012.net.il by mtaout29.012.net.il (HyperSendmail v2007.08) id <0NC500000S1IJE00@mtaout29.012.net.il>; Fri, 19 Sep 2014 20:34:18 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout29.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NC5002WKST58V00@mtaout29.012.net.il>; Fri, 19 Sep 2014 20:34:18 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.185 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:174565 Archived-At: > From: Glenn Morris > Cc: emacs-devel@gnu.org > Date: Fri, 19 Sep 2014 12:49:13 -0400 > > Less flippantly, more concentrated focus on the release, less "a handful > of people try to get the release in shape while the majority play with > the trunk (and argue about VCS)". I can't agree more, but the question is how to reach that goal? > (But this might just be my biased impression.) My impression is similar, FWIW. > Also a defined release manager position, with the authority > to set deadlines and decide what needs to be done, which I think was > lacking this time. (I don't want the job; it needs to be someone > motivated and with Emacs experience.) We need a volunteer, yes. > And more documenting of changes closer to the time they happen, by the > person who makes the change, rather than leaving it to the end. I suggested that once, but the suggestion was rejected. I still think it's a good policy, successfully implemented in other projects. > We have ~ 200 developers, in theory. I think say 6 months from feature > freeze to release ought to be doable, though I would not want to be > dogmatic about it; it should take as long as it takes. > > When it takes too long, people get disheartened and lose focus. I absolutely agree, but the problem is a practical one; I think we are all together on the principles front.