From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: npostavs@gmail.com, emacs-devel@gnu.org
Subject: Re: Future release of emacs-26
Date: Mon, 27 May 2019 11:05:08 +0200 [thread overview]
Message-ID: <874l5guv23.fsf@russet.org.uk> (raw)
In-Reply-To: <83o93u774z.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 22 May 2019 20:04:28 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> 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.
Okay. But I would think that it needs to be sooner rather than
later. The time could disappear very rapidly with summer coming up. Even
as it stands, there may be many GNU/Linux distributions that will not
update before the key runs out which is a bit messy.
Phil
next prev parent reply other threads:[~2019-05-27 9:05 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 4:55 bug#34341: 26.1; url-retrieve-synchronously returns blank buffer Laurent Charignon
2019-02-06 8:12 ` bug#34341: Seems fixed in latest master 5259fdf96073febd18e83785960c443bdf02a310 Laurent Charignon
2019-02-09 18:08 ` bug#34341: more observations Mikhail Rudenko
2019-05-04 15:18 ` bug#34341: 26.1; url-retrieve-synchronously returns blank buffer Noam Postavsky
2019-05-06 11:52 ` Robert Pluim
2019-05-06 12:10 ` Noam Postavsky
2019-05-06 12:15 ` Robert Pluim
2019-05-06 15:21 ` Eli Zaretskii
2019-05-07 0:16 ` Noam Postavsky
2019-05-07 2:36 ` Eli Zaretskii
2019-05-07 6:35 ` Robert Pluim
2019-05-12 13:01 ` Robert Pluim
2019-05-12 14:02 ` Eli Zaretskii
2019-05-12 14:55 ` Robert Pluim
2019-05-12 15:23 ` Eli Zaretskii
2019-05-12 15:39 ` Robert Pluim
2019-05-12 16:01 ` Eli Zaretskii
2019-05-14 0:21 ` Noam Postavsky
2019-05-14 0:34 ` Future release of emacs-26 (WAS: bug#34341) Noam Postavsky
2019-05-14 12:11 ` 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874l5guv23.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=npostavs@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.