From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: [ANNOUNCE] Emacs 25.3 released Date: Wed, 13 Sep 2017 00:07:00 -0700 Organization: UCLA Computer Science Department Message-ID: References: <87wp55t0un.fsf@petton.fr> <87r2vctasb.fsf@petton.fr> <87mv60t6sk.fsf@petton.fr> <837ex4q6uy.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1505286456 5251 195.159.176.226 (13 Sep 2017 07:07:36 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 13 Sep 2017 07:07:36 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 Cc: nicolas@petton.fr, rostislav.svoboda@gmail.com, emacs-devel@gnu.org To: Andreas Schwab , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 13 09:07:29 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ds1lX-0000ec-1O for ged-emacs-devel@m.gmane.org; Wed, 13 Sep 2017 09:07:19 +0200 Original-Received: from localhost ([::1]:40477 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ds1ld-00016z-Km for ged-emacs-devel@m.gmane.org; Wed, 13 Sep 2017 03:07:25 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42966) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ds1lN-00015R-Mu for emacs-devel@gnu.org; Wed, 13 Sep 2017 03:07:10 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ds1lM-00022n-N3 for emacs-devel@gnu.org; Wed, 13 Sep 2017 03:07:09 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:36456) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ds1lI-0001xC-Oi; Wed, 13 Sep 2017 03:07:04 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 3E5A5160D03; Wed, 13 Sep 2017 00:07:02 -0700 (PDT) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id O3Anic6CnqHa; Wed, 13 Sep 2017 00:07:01 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 7B2A7160D06; Wed, 13 Sep 2017 00:07:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id IiTzbXne2kEI; Wed, 13 Sep 2017 00:07:01 -0700 (PDT) Original-Received: from [192.168.1.9] (unknown [47.153.184.153]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 42675160D01; Wed, 13 Sep 2017 00:07:01 -0700 (PDT) In-Reply-To: Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 131.179.128.68 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:218172 Archived-At: Andreas Schwab wrote: > It's all about trust. And especially in the context of security, trust > is the most important thing. You're right. Security-minded users need to be suspicious when new software releases are made out of the blue. Having an emergency release tagged and publicly visible in the repository can help allay these natural suspicions. We don't have much practice making emergency Emacs releases because we don't often make them (which is a good thing!). That being said, the next time it happens we should try to have a smoother rollout, and having a properly tagged commit should be part of that. This will help avoid this particular confusion next time. Another thing I'd like is a faster rollout. We were publicly notified of the bug on September 4 and did not announce a new release containing a small fix until over a week later. Although there were reasons for the delay, it would be better to get announcements and fixes out faster. I've had multiple offers from others to help, and would like to take up at least one of these offers. Of course trust is an important concern here as well.