From: Mekeor Melire <mekeor@posteo.de>
To: Andrew Tropin <andrew@trop.in>
Cc: 63984@debbugs.gnu.org, liliana.prikler@gmail.com
Subject: [bug#63984] [PATCH emacs-team 0/2] Start preparing for Emacs 29
Date: Sun, 11 Jun 2023 21:09:54 +0000 [thread overview]
Message-ID: <87sfaxwv18.fsf@posteo.de> (raw)
In-Reply-To: <871qiipnmt.fsf@trop.in>
Hello :)
2023-06-11 09:35 andrew@trop.in:
> Sounds reasonable, but I think it would be ok, if after updating
> emacs, emacs-next will be 29 for a couple of weeks with
> deprecation warning on top of it. The meaning of -next suffix is
> a convention, not a technical limitation, so it's fine to
> violate it for deprecation period.
> Overall, deprecation is not something crucial here and people
> know that guix breaks backward compatibility from time to time,
> so I think it's ok to go without it.
I think we don't need to divert deprecation/alias from its
intended use. I think NEWS serves its job well enough.
When having emacs-next installed and keeping it upgraded, users
should be able to expect that the upcoming release of Emacs is
installed, without deprecation warnings. After all, the package is
not called emacs29 but emacs-next.
That being said, I believe it's a good idea to
define-deprecated/public-alias emacs-next-pgtk and
emacs-next-pgtk-xwidgets.
next prev parent reply other threads:[~2023-06-11 21:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 16:22 [bug#63984] [PATCH emacs-team 0/2] Start preparing for Emacs 29 Liliana Marie Prikler
2023-06-09 8:40 ` [bug#63984] [PATCH emacs-team 1/2] gnu: Make emacs-next-tree-sitter the new emacs Liliana Marie Prikler
2023-06-09 11:28 ` [bug#63984] [PATCH emacs-team 2/2] gnu: Construct Emacs packages from bottom up Liliana Marie Prikler
2023-06-10 6:46 ` [bug#63984] [PATCH emacs-team 0/2] Start preparing for Emacs 29 Andrew Tropin
2023-06-10 7:46 ` Liliana Marie Prikler
2023-06-10 8:20 ` Andrew Tropin
2023-06-10 8:51 ` Liliana Marie Prikler
2023-06-11 5:35 ` Andrew Tropin
2023-06-11 21:09 ` Mekeor Melire [this message]
2023-06-12 4:30 ` Andrew Tropin
2023-07-04 7:39 ` Mekeor Melire
2023-07-08 17:04 ` Liliana Marie Prikler
2023-07-12 18:15 ` Mekeor Melire
2023-07-13 16:20 ` bug#63984: " Liliana Marie Prikler
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfaxwv18.fsf@posteo.de \
--to=mekeor@posteo.de \
--cc=63984@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=liliana.prikler@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/guix.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).