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 01:53:08 -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> <87tw07rqqg.fsf@petton.fr> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1505292836 17191 195.159.176.226 (13 Sep 2017 08:53:56 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 13 Sep 2017 08:53:56 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 Cc: rostislav.svoboda@gmail.com, emacs-devel@gnu.org To: Nicolas Petton , Andreas Schwab , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 13 10:53:51 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 1ds3Qc-0004MS-Eo for ged-emacs-devel@m.gmane.org; Wed, 13 Sep 2017 10:53:50 +0200 Original-Received: from localhost ([::1]:40988 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ds3Qj-0005Mt-IL for ged-emacs-devel@m.gmane.org; Wed, 13 Sep 2017 04:53:57 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54307) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ds3Q5-0005Ml-Un for emacs-devel@gnu.org; Wed, 13 Sep 2017 04:53:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ds3Q5-0004lk-2v for emacs-devel@gnu.org; Wed, 13 Sep 2017 04:53:18 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:41916) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ds3Py-0004UO-Pj; Wed, 13 Sep 2017 04:53:10 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 8E9AA160CC8; Wed, 13 Sep 2017 01:53:09 -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 rbRPElqIXYZ1; Wed, 13 Sep 2017 01:53:08 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id C416C160D02; Wed, 13 Sep 2017 01:53:08 -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 HD2Yxvn_4rzO; Wed, 13 Sep 2017 01:53:08 -0700 (PDT) Original-Received: from [192.168.1.9] (unknown [47.153.184.153]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 959EA1600B0; Wed, 13 Sep 2017 01:53:08 -0700 (PDT) In-Reply-To: <87tw07rqqg.fsf@petton.fr> 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:218178 Archived-At: Nicolas Petton wrote: > First, if I'm not being trusted with the release tarballs, somebody els= e > can build them next time. >=20 > Second, you can easily diff the emacs-25.3 tarball against emacs-25.2. >=20 > Even if I did create a branch and tag before publishing the tarball, > you'd have no guarantee that the tarball actually contains the content > of the git commit. Diffing is the only way for you to see the actual > changes. All quite true. Still, trust is typically established by multiple means. = Many=20 users won't have time to track down where the diff was published or to re= ad the=20 diff, or they won't have the technical ability to understand the diff's=20 implications. And many users won't know who you are. But if these users t= rust=20 savannah.gnu.org, a tagged commit there can be enough for them so that th= ey=20 don't have to do the other stuff. (And there may be some very cautious us= ers who=20 want to do all of the above....) So it is helpful to have a tagged commit at the time of release, even tho= ugh a=20 tag by itself is not enough to satisfy the most-cautious, and even though= many=20 users don't care about the tag. Some background here. I've managed releases for the public-domain time zo= ne=20 database (tzdb) for several years. Some of my correspondents there are *q= uite*=20 cautious, way more cautious than anything mentioned in this thread. They = have=20 asked for multiple ways to verify that each release is what it purports t= o be,=20 beyond what I thought was needed. But they're *users*. They know their ne= eds=20 better than I do. And if they say they want SHA-512 checksums in addition= to GPG=20 checksums, who am I to tell them that they're redundant? I want them to t= rust=20 the tzdb distribution, so I try to accommodate their concerns, not to arg= ue with=20 them.