unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: emacs-devel@gnu.org
Subject: Future release of emacs-26 (WAS: bug#34341)
Date: Mon, 13 May 2019 20:34:48 -0400	[thread overview]
Message-ID: <87y339g9g7.fsf_-_@gmail.com> (raw)
In-Reply-To: <83k1f3k3rm.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 06 May 2019 18:21:17 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> and we don't even know whether emacs-26 will be
> used for another "regular" release.

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



       reply	other threads:[~2019-05-14  0:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+7=K2gfxsgW7sUCLR7294kcA1kG+-0FSqL1wmdq2U5s8v2Syw@mail.gmail.com>
     [not found] ` <871s1ent89.fsf@gmail.com>
     [not found]   ` <m2pnovu7es.fsf@gmail.com>
     [not found]     ` <87pnovlr5z.fsf@gmail.com>
     [not found]       ` <m2lfzju6cg.fsf@gmail.com>
     [not found]         ` <83k1f3k3rm.fsf@gnu.org>
2019-05-14  0:34           ` Noam Postavsky [this message]
2019-05-14 12:11             ` Future release of emacs-26 (WAS: bug#34341) Nicolas Petton
2019-05-14 13:25             ` Future release of emacs-26 Stefan Monnier
2019-05-14 15:32             ` Future release of emacs-26 (WAS: bug#34341) Eli Zaretskii
2019-05-14 20:34             ` Richard Copley
2019-05-14 21:03               ` Future release of emacs-26 Stefan Monnier
2019-05-14 21:28                 ` Richard Copley
2019-05-15  1:27                   ` Stefan Monnier
2019-05-17  0:03                     ` Stephen Leake
2019-05-17  3:03                       ` Stefan Monnier
2019-05-17  6:17                         ` Richard Copley
2019-05-22 16:07             ` Phillip Lord
2019-05-22 16:26               ` Stefan Monnier
2019-05-22 17:04               ` Eli Zaretskii
2019-05-23 10:09                 ` Leo Liu
2019-05-27  9:05                 ` Phillip Lord
2019-05-27 16:13                   ` Eli Zaretskii
2019-05-27 20:17                     ` Richard Stallman
2019-05-28  2:37                       ` Eli Zaretskii
2019-05-28 21:41                     ` Noam Postavsky
2019-06-02 18:42                     ` Phillip Lord
2019-06-02 20:34                       ` Stefan Monnier
2019-06-03 14:22                     ` Noam Postavsky
2019-06-03 14:53                       ` Eli Zaretskii
2019-06-03 15:45                         ` Noam Postavsky
2019-06-03 16:00                           ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y339g9g7.fsf_-_@gmail.com \
    --to=npostavs@gmail.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).