From: Po Lu <luangruo@yahoo.com>
To: Bastien <bzg@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
emacs-devel@gnu.org, Ihor Radchenko <yantar92@gmail.com>,
Kyle Meyer <kyle@kyleam.com>
Subject: Re: Tentative release schedule for Emacs 29.1
Date: Wed, 16 Nov 2022 12:52:17 +0800 [thread overview]
Message-ID: <87a64rfqm6.fsf@yahoo.com> (raw)
In-Reply-To: <87fsejv7a5.fsf@bzg.fr> (Bastien's message of "Wed, 16 Nov 2022 05:43:14 +0100")
Bastien <bzg@gnu.org> writes:
> Hi Lars,
>
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> We're aiming to cut the new release branch in late November.
>
> Is it still the plan?
>
> Ideally, a 2-3 weeks delay between Emacs 29.1 and Org 9.6 would help
> us fix new bugs and release 9.6.1 to be included in Emacs 29.1.
>
> Given that delay and given Emacs release expectations, what would be
> the best time to release Org?
>
> If we can release 9.6 in late november and fix bugs until mid-december
> then release and sync 9.6.1, that'd be great.
>
> Thanks,
I think we should not cut the branch until bug#59183 is fixed. I run
into that serious crash every few days.
next prev parent reply other threads:[~2022-11-16 4:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 15:03 Tentative release schedule for Emacs 29.1 Lars Ingebrigtsen
2022-09-24 6:44 ` Bastien
2022-09-24 10:32 ` Lars Ingebrigtsen
2022-09-24 16:24 ` Bastien
2022-11-16 4:43 ` Bastien
2022-11-16 4:52 ` Po Lu [this message]
2022-11-16 13:12 ` Eli Zaretskii
2022-11-16 13:26 ` Po Lu
2022-11-16 13:52 ` Eli Zaretskii
2022-11-16 13:51 ` Stefan Monnier
2022-11-16 13:59 ` Eli Zaretskii
2022-11-16 13:09 ` Eli Zaretskii
2022-11-16 13:23 ` Bastien
2022-11-16 13:50 ` Eli Zaretskii
2022-11-16 14:53 ` Bastien
2022-11-16 16:45 ` 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=87a64rfqm6.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kyle@kyleam.com \
--cc=larsi@gnus.org \
--cc=yantar92@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/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).