From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Future release of emacs-26 Date: Wed, 22 May 2019 20:04:28 +0300 Message-ID: <83o93u774z.fsf@gnu.org> References: <871s1ent89.fsf@gmail.com> <87pnovlr5z.fsf@gmail.com> <83k1f3k3rm.fsf@gnu.org> <87y339g9g7.fsf_-_@gmail.com> <87sgt6321t.fsf@russet.org.uk> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="194669"; mail-complaints-to="usenet@blaine.gmane.org" Cc: npostavs@gmail.com, emacs-devel@gnu.org To: phillip.lord@russet.org.uk (Phillip Lord) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 22 19:06:28 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 1hTUh9-000oPg-MQ for ged-emacs-devel@m.gmane.org; Wed, 22 May 2019 19:06:27 +0200 Original-Received: from localhost ([127.0.0.1]:47977 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hTUh8-0004y6-Il for ged-emacs-devel@m.gmane.org; Wed, 22 May 2019 13:06:26 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:40667) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hTUfC-0003YL-Ss for emacs-devel@gnu.org; Wed, 22 May 2019 13:04:27 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:41277) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hTUfB-0007mB-37; Wed, 22 May 2019 13:04:26 -0400 Original-Received: from [176.228.60.248] (port=3249 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hTUf7-0001oI-SD; Wed, 22 May 2019 13:04:22 -0400 In-reply-to: <87sgt6321t.fsf@russet.org.uk> (phillip.lord@russet.org.uk) 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:236906 Archived-At: > From: phillip.lord@russet.org.uk (Phillip Lord) > Date: Wed, 22 May 2019 17:07:58 +0100 > Cc: emacs-devel@gnu.org > > > So, I'm thinking we should be aiming for another "regular" release > > around September, when the GNU ELPA package signing key expires. After > > that, people downloading Emacs 26.2 won't be able to install GNU ELPA > > packages without either disabling signature checking, or manually > > installing the new key. > > > > https://debbugs.gnu.org/35414 > > https://elpa.gnu.org/packages/gnu-elpa-keyring-update.html > > > Another possibility would be to release Emacs-26.2.1 which is just > Emacs-26.2 with the key updated. We don't release X.Y.Z versions. For starters, it gets in the way of local build numbering. We could, of course, release Emacs 26.3 with just the key update, but IMO, given the effort required to put a tarball out the door, it would make more sense to have the fixes we backported since 26.2 as well. > This could be done with a single commit and would not require an > extensive pre-test period. 26.3 from the current branch should not require an extensive pretest either. > It seems problematic to me to tie a release cycle to a key running > out. We don't. We just use that as a pretense for another 26.x release.