unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Christopher Howard <christopher@librehacker.com>
Cc: emacs-devel@gnu.org, emacsconf-discuss@gnu.org
Subject: Re: Emacs 30 Release?
Date: Thu, 22 Aug 2024 20:49:49 +0300	[thread overview]
Message-ID: <86cym0sb0i.fsf@gnu.org> (raw)
In-Reply-To: <8734mwzfac.fsf@librehacker.com> (message from Christopher Howard on Thu, 22 Aug 2024 08:35:39 -0800)

> From: Christopher Howard <christopher@librehacker.com>
> Cc: emacs-devel@gnu.org, emacsconf-discuss@gnu.org
> Date: Thu, 22 Aug 2024 08:35:39 -0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Christopher Howard <christopher@librehacker.com>
> >> Date: Wed, 21 Aug 2024 13:43:03 -0800
> >> 
> >> Hi, I'm just curious how close we might be to the 30 release. Mostly just eager anticipation, but I was also trying to make plans for my EmacsConf videos.
> >
> > The first pretest of Emacs 30 is in the works as we speak.  How long
> > it takes before the actual release will depend on the results of the
> > pretest -- if it turns out very stable with a few minor bug reports or
> > none at all, the actual release will follow quickly, in a month or so.
> > Failing that, it might take another month or maybe two.
> 
> Thanks, do you have plans to report back with the results of the pre-test, or should I bug you again in a week or two?

I wouldn't know what to report.

Why is it important for you to be informed on the progress of the
pretest?

> For my part, I don't really want to use Emacs 30 before it is properly released, but also I needed a decent amount of time to play around with it before the EmacsConf video upload deadline (Nov 8th). I suppose other uploaders are thinking the same thing, except for those who use bleeding edge Emacs. Hence the inquiry into this. I am not trying to rush you or anything.

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.



  parent reply	other threads:[~2024-08-22 17:49 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 [this message]
2024-08-22 19:39       ` Christopher Howard
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=86cym0sb0i.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=christopher@librehacker.com \
    --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).