From: Eli Zaretskii <eliz@gnu.org>
To: Troy Hinckley <comms@dabrev.com>
Cc: emacs-devel@gnu.org, stefankangas@gmail.com
Subject: Re: Emacs 28.3 Release
Date: Mon, 10 Apr 2023 16:20:23 +0300 [thread overview]
Message-ID: <83r0src1rc.fsf@gnu.org> (raw)
In-Reply-To: <9ea47b22-f2d8-4225-b5f2-966ca0d797f9@Spark> (message from Troy Hinckley on Mon, 10 Apr 2023 08:05:04 -0500)
> Date: Mon, 10 Apr 2023 08:05:04 -0500
> From: Troy Hinckley <comms@dabrev.com>
>
> I am asking again what we can do to complete the Emacs 28.3 release. My concern is that we have a
> narrow window in which this version will be viable. As it currently stands the latest stable release has a
> high severity CVE that prevents Emacs from being installed in security sensitive domains. 28.3 will
> resolve that and make the latest stable release usable. However, someone will inevitably find another
> CVE against Emacs. At that point 28.3 will no longer be useful. Given how hard it has been to get this
> release, I doubt there would be resources to add another security patch to Emacs 28.
>
> I am requesting to see if there is anything the community can do to help complete this release before
> it becomes irrelevant. The release candidate has been out for couple months at this point.
Stefan was working on 28.3, prepared an RC, and is silent for the last
4 weeks or so. I think any work on this should pick up where he left
off, but for that we need him to tell us where he left off...
next prev parent reply other threads:[~2023-04-10 13:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f4b95933-46bd-4bcb-b9ca-ceed72b1c6ee@Spark>
2023-04-10 13:05 ` Emacs 28.3 Release Troy Hinckley
2023-04-10 13:20 ` Eli Zaretskii [this message]
2023-04-10 14:33 ` lux
2023-04-10 14:44 ` Ulrich Mueller
2023-04-10 14:46 ` lux
2023-04-10 13:50 ` Po Lu
2023-04-11 8:14 ` Jean Louis
2023-04-12 15:37 ` Troy Hinckley
2023-04-12 16:31 ` lux
2023-04-12 16:56 ` Corwin Brust
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=83r0src1rc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=comms@dabrev.com \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@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 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).