From: Karl Fogel <kfogel@red-bean.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 28.2 released
Date: Mon, 12 Sep 2022 15:59:38 -0500 [thread overview]
Message-ID: <87wna8ia11.fsf@red-bean.com> (raw)
In-Reply-To: <CADwFkmnx-h5uhfM3jgkaBK5B-HpfOkCAgDs4uFoQQtftCpBKSw@mail.gmail.com> (Stefan Kangas's message of "Mon, 12 Sep 2022 06:13:13 -0400")
Congratulations on the release!
Since these release announcement emails are widely shared (I saw
this one appear on news.ycombinator.com, for example), it might be
good to include a link to corresponding release notes.
That could be a link to an appropriate named anchor on
https://www.gnu.org/savannah-checkouts/gnu/emacs/emacs.html#Releases
(but there do not appear to be release-specific anchors on that
page currently, so we'd have to add that to release process).
Or it could be a link directly to the plaintext release notes that
the above web page points to anyway; in this case, that would be
https://www.gnu.org/savannah-checkouts/gnu/emacs/news/NEWS.28.1.
Either way, it would be helpful to those who see these release
announcements to be able to go directly from the announcement to a
page that tells them what's new in that release.
Best regards,
-Karl
On 12 Sep 2022, Stefan Kangas wrote:
>Version 28.2 of Emacs, the extensible text editor, should now
>be available from your nearest GNU mirror:
>
> https://ftpmirror.gnu.org/emacs/emacs-28.2.tar.xz
> https://ftpmirror.gnu.org/emacs/emacs-28.2.tar.gz
>
>The tarball is signed; you can get the PGP signature file at:
>
> https://ftpmirror.gnu.org/emacs/emacs-28.2.tar.xz.sig
> https://ftpmirror.gnu.org/emacs/emacs-28.2.tar.gz.sig
>
>You can choose a mirror explicitly from the list at:
> https://www.gnu.org/prep/ftp.html
>
>Mirrors may take some time to update; the main GNU FTP server is
>at:
> https://ftp.gnu.org/gnu/emacs/
>
>To verify that the downloaded tarball is intact, download both
>the
>tarball and the corresponding .sig file, and run this command:
>
> gpg --verify emacs-28.2.tar.xz.sig
>
>(and similarly for emacs-28.2.tar.gz, if you download that
>format).
>
>If the GPG command fails because you don't have the required PGP
>public key, run this command to import the key:
>
> gpg --keyserver pgp.mit.edu --recv-keys \
> CEA1DE21AB108493CC9C65742E82323B8F4353EE
>
>Alternative keyservers to try are keyserver.ubuntu.com and
>keys.openpgp.org.
>
>You can also run sha1sum or sha256sum and confirm that these
>checksums match:
>
>SHA1 emacs-28.2.tar.xz
>d61863db02b732547e6d6c77081e3348734458be
>SHA1 emacs-28.2.tar.gz
>b019ec832c73cd8548981fe2bc11a7d6e812ddb9
>
>SHA256 emacs-28.2.tar.xz
>ee21182233ef3232dc97b486af2d86e14042dbb65bbc535df562c3a858232488
>SHA256 emacs-28.2.tar.gz
>a6912b14ef4abb1edab7f88191bfd61c3edd7085e084de960a4f86485cb7cad8
>
>Emacs 28.2 is a bug-fix release, with no new features with
>respect to
>Emacs 28.1.
>
>For the complete list of changes and the people who made them,
>see the
>various ChangeLog files in the source distribution. For a
>summary of
>all the people who have contributed to Emacs, see the etc/AUTHORS
>file.
>
>The online manuals and website will be updated shortly.
>
>Printed copies of the Emacs manual are available for purchase
>from the
>Free Software Foundation's online store at:
> https://shop.fsf.org/product/emacs-manual/
>
>For more information about Emacs, see:
> https://www.gnu.org/software/emacs
next prev parent reply other threads:[~2022-09-12 20:59 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 10:13 Emacs 28.2 released Stefan Kangas
2022-09-12 11:28 ` Michael Albinus
2022-09-12 11:55 ` Michael Albinus
2022-09-12 11:59 ` Eli Zaretskii
2022-09-12 12:00 ` Eli Zaretskii
2022-09-12 12:03 ` Michael Albinus
2022-09-12 12:20 ` Lars Ingebrigtsen
2022-09-12 20:59 ` Karl Fogel [this message]
2022-09-13 1:36 ` Stefan Kangas
2022-09-13 2:30 ` Eli Zaretskii
2022-09-13 9:39 ` Stefan Kangas
2022-09-13 12:03 ` Eli Zaretskii
2022-09-13 12:46 ` Stefan Kangas
2022-09-13 13:03 ` Lars Ingebrigtsen
2022-09-13 13:43 ` Robert Pluim
2022-09-13 13:55 ` Lars Ingebrigtsen
2022-09-14 16:43 ` Stefan Kangas
2022-09-14 16:47 ` Lars Ingebrigtsen
2022-09-14 17:33 ` Eli Zaretskii
2022-09-14 22:50 ` Stefan Kangas
2022-09-15 5:37 ` Eli Zaretskii
2022-09-15 7:44 ` Stefan Kangas
2022-09-14 16:54 ` Eli Zaretskii
2022-09-14 22:50 ` Stefan Kangas
2022-09-15 5:38 ` Eli Zaretskii
2022-09-14 16:57 ` Karl Fogel
2022-09-14 18:34 ` Bob Rogers
2022-09-16 14:56 ` Stefan Kangas
2022-09-13 15:29 ` Karl Fogel
2022-09-13 15:49 ` Eli Zaretskii
2022-09-13 15:52 ` Eli Zaretskii
2022-09-14 16:59 ` Karl Fogel
2022-09-14 17:04 ` Eli Zaretskii
2022-09-13 17:23 ` Windows Binaries for " Corwin Brust
2022-09-13 17:47 ` Eli Zaretskii
2022-09-13 18:01 ` Corwin Brust
2022-09-13 18:13 ` Eli Zaretskii
2022-09-13 19:30 ` Corwin Brust
2022-09-13 18:27 ` Óscar Fuentes
2022-09-14 2:56 ` Corwin Brust
2022-09-13 23:11 ` Corwin Brust
2022-09-14 2:36 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2022-09-14 17:06 Karl Fogel
2022-09-14 17:21 ` Eli Zaretskii
2022-09-14 18:49 ` Karl Fogel
2022-09-14 18:56 ` Eli Zaretskii
2022-09-14 19:15 ` Karl Fogel
2022-09-14 19:21 ` Eli Zaretskii
2022-09-14 19:53 ` Karl Fogel
2022-09-15 6:58 ` Eli Zaretskii
2022-09-15 7:44 ` Stefan Kangas
2022-09-15 17:59 ` Karl Fogel
2022-09-14 17:39 ` 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=87wna8ia11.fsf@red-bean.com \
--to=kfogel@red-bean.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 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.