From: Eli Zaretskii <eliz@gnu.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: emacs-devel@gnu.org
Subject: Re: Will there be an Emacs 28.3 release?
Date: Sun, 04 Jun 2023 15:01:25 +0300 [thread overview]
Message-ID: <83r0qr5td6.fsf@gnu.org> (raw)
In-Reply-To: <u7csjzdw5@gentoo.org> (message from Ulrich Mueller on Sun, 04 Jun 2023 13:05:14 +0200)
> From: Ulrich Mueller <ulm@gentoo.org>
> Date: Sun, 04 Jun 2023 13:05:14 +0200
>
> The 28.3-rc1 release candidate appeared on 2023-02-19 which was more
> than three months ago. The statement at the time was that the 28.3
> release would be made "hopefully already later today" but apparently
> that hasn't happened. There's also no activity on the emacs-28 branch
> since February. Meanwhile, the pretest for 29.1 has started.
>
> So, will there be an 28.3 release at all?
Only if someone steps forward to finish the job started by Stefan
Kangas, who prepared the RC. I myself cannot afford adding that to
what I have to do already, including the v29.1 release process.
Sorry.
> I am asking because Gentoo has a package for the release candidate with
> testing keywords since February, and I wonder what will be the way
> forward. If it was certain that there won't be a 28.3 release, then we
> would presumably label our 28.3_rc1 package as stable and drop 28.2.
> (It has seen three months of testing after all. :)
I think making your own 28.3 release is a good move, all things
considering.
prev parent reply other threads:[~2023-06-04 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 11:05 Will there be an Emacs 28.3 release? Ulrich Mueller
2023-06-04 12:01 ` Eli Zaretskii [this message]
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=83r0qr5td6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ulm@gentoo.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 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.