From: Christopher Howard <christopher@librehacker.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, emacsconf-discuss@gnu.org
Subject: Re: Emacs 30 Release?
Date: Thu, 22 Aug 2024 11:39:02 -0800 [thread overview]
Message-ID: <8734mwny95.fsf@librehacker.com> (raw)
In-Reply-To: <86cym0sb0i.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 22 Aug 2024 20:49:49 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I wouldn't know what to report.
>
> Why is it important for you to be informed on the progress of the
> pretest?
>
You made it sound like after the pre-test, you would know whether it was "mostly stable" or not, and thus some idea of whether it might be one month or three months until a release.
>
> We never really know in advance when the release is imminent, except
> when we produce a release candidate. So just watching out for RC1
> should be a good idea.
Okay. Sounds like I might as well just build Emacs 30 now and start playing around with it. I'm going to make a random guess and suppose that the git branch I want is the "emacs-30" branch.
--
Christopher Howard
next prev parent reply other threads:[~2024-08-22 19:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 21:43 Emacs 30 Release? Christopher Howard
2024-08-22 3:50 ` Eli Zaretskii
2024-08-22 16:35 ` Christopher Howard
2024-08-22 16:56 ` : " Robert Pluim
2024-08-22 17:24 ` Juergen Fenn
2024-08-22 17:49 ` Eli Zaretskii
2024-08-22 19:39 ` Christopher Howard [this message]
2024-08-23 22:41 ` Stefan Kangas
2024-08-26 17:01 ` Christopher Howard
2024-08-26 17:49 ` Eli Zaretskii
2024-08-28 15:21 ` Post-Upgrade Breakage Philip Kaludercic
2024-09-01 20:15 ` Emacs 30 Release? pinmacs
2024-09-01 20:24 ` pinmacs
2024-09-02 11:20 ` 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
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=8734mwny95.fsf@librehacker.com \
--to=christopher@librehacker.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacsconf-discuss@gnu.org \
/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).