From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.devel Subject: Re: Emacs 26.2 RC1 is out! Date: Fri, 22 Mar 2019 12:39:44 -0400 Message-ID: References: <87o965nq4q.fsf@petton.fr> <87ftrgod5o.fsf@petton.fr> <87o964kl4p.fsf@petton.fr> <83a7hntn2c.fsf@gnu.org> <87lg17l1xi.fsf@petton.fr> <83k1grs283.fsf@gnu.org> <877ecrl06s.fsf@petton.fr> <83imwbs0ip.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="235031"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) Cc: Nicolas Petton , andrewjmoreton@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 22 18:14:43 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h7Nkh-000yyc-By for ged-emacs-devel@m.gmane.org; Fri, 22 Mar 2019 18:14:43 +0100 Original-Received: from localhost ([127.0.0.1]:60430 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h7Nkg-0001fY-BP for ged-emacs-devel@m.gmane.org; Fri, 22 Mar 2019 13:14:42 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:47880) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h7NSu-0002tX-9A for emacs-devel@gnu.org; Fri, 22 Mar 2019 12:56:23 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:45682) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h7NCx-0005JG-Vc; Fri, 22 Mar 2019 12:39:52 -0400 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1h7NCs-0003Wc-PA; Fri, 22 Mar 2019 12:39:46 -0400 X-Spook: National infrastructure Magnitude digicash DNDO sweep X-Ran: g?KVtw,46.AyL!^UT%m't-/5!${@zzcUhTCg';U|dJ-.kK{kT_iJ?UR&z{a:ihj+3%}ng) X-Hue: brightred X-Attribution: GM In-Reply-To: <83imwbs0ip.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 22 Mar 2019 11:48:14 +0200") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:234607 Archived-At: >> > Which are the affected files? >> >> README >> configure.ac >> etc/HISTORY >> msdos/sed2v2.inp >> nt/README.W32 The instructions are probably unclear. The intent was that you would M-x set-version, commit, tag, push. It was just the HISTORY and ChangeLog file with the release notice that would not be committed, in case the release date had to change. It would not do any harm to commit those two files as well (ChangeLog is no longer versioned, but those changes get committed as ChangeLog.3 or whatever). It just creates a bit of churn if the release date ends up changing, and obviously those files two don't affect the build in any way, so personally I see no reason to commit them. Testing from git is not the same as testing the release tarball, because the tarball includes many generated files that certainly do affect the build (configure, elc files, etc). BTW, looks like none of the 26.2.x pretests (or RC) were tagged. Since other changes have since been committed to emacs-26, but the version number change wasn't, it's not really possible to tag the RC now.