From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: "Perry E. Metzger" Newsgroups: gmane.emacs.devel Subject: Alerting users to new releases Date: Tue, 12 Sep 2017 17:59:21 -0400 Message-ID: <20170912175921.6503935d@jabberwock.cb.piermont.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1505253598 15445 195.159.176.226 (12 Sep 2017 21:59:58 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 12 Sep 2017 21:59:58 +0000 (UTC) To: Emacs Devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Sep 12 23:59:48 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 1drtDV-0003AT-UC for ged-emacs-devel@m.gmane.org; Tue, 12 Sep 2017 23:59:38 +0200 Original-Received: from localhost ([::1]:38844 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1drtDd-00032C-Bz for ged-emacs-devel@m.gmane.org; Tue, 12 Sep 2017 17:59:45 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56551) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1drtDP-0002xE-Ob for emacs-devel@gnu.org; Tue, 12 Sep 2017 17:59:32 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1drtDM-0006WE-SL for emacs-devel@gnu.org; Tue, 12 Sep 2017 17:59:31 -0400 Original-Received: from hacklheber.piermont.com ([166.84.7.14]:54110) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1drtDM-0006SC-MZ for emacs-devel@gnu.org; Tue, 12 Sep 2017 17:59:28 -0400 Original-Received: from snark.cb.piermont.com (localhost [127.0.0.1]) by hacklheber.piermont.com (Postfix) with ESMTP id 5CE31125 for ; Tue, 12 Sep 2017 18:00:53 -0400 (EDT) Original-Received: from jabberwock.cb.piermont.com (jabberwock.cb.piermont.com [10.160.2.107]) by snark.cb.piermont.com (Postfix) with ESMTP id 5DA722DF10E for ; Tue, 12 Sep 2017 17:59:21 -0400 (EDT) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 166.84.7.14 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:218159 Archived-At: As it stands, when a security vuln shows up, and a new release gets pushed out, there isn't a good way to alert the vast majority of users to its presence. One way such things are handled these days for a lot of projects is to have the code periodically check if a newer version of the software is available. Would it be reasonable if a feature was added to Emacs to alert the user that a newer version of Emacs existed? Or would the potential privacy issues, even if the check could be turned off, exceed the benefit? Perry -- Perry E. Metzger perry@piermont.com