all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Troy Hinckley <comms@dabrev.com>
To: emacs-devel@gnu.org, Eli Zaretskii <eliz@gnu.org>,
	Stefan Kangas <stefankangas@gmail.com>
Subject: Emacs 28.3 Release
Date: Mon, 10 Apr 2023 08:05:04 -0500	[thread overview]
Message-ID: <9ea47b22-f2d8-4225-b5f2-966ca0d797f9@Spark> (raw)
In-Reply-To: f4b95933-46bd-4bcb-b9ca-ceed72b1c6ee@Spark

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

Hi Emacs devs,
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.

— Troy Hinckley

[-- Attachment #2: Type: text/html, Size: 1033 bytes --]

       reply	other threads:[~2023-04-10 13:05 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 ` Troy Hinckley [this message]
2023-04-10 13:20   ` Emacs 28.3 Release Eli Zaretskii
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

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

  git send-email \
    --in-reply-to=9ea47b22-f2d8-4225-b5f2-966ca0d797f9@Spark \
    --to=comms@dabrev.com \
    --cc=eliz@gnu.org \
    --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 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.