From: Bastien <bzg@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, emacs-devel@gnu.org, yantar92@gmail.com, kyle@kyleam.com
Subject: Re: Tentative release schedule for Emacs 29.1
Date: Wed, 16 Nov 2022 14:23:11 +0100 [thread overview]
Message-ID: <87k03vvxs0.fsf@gnu.org> (raw)
In-Reply-To: <83k03vgi6c.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 16 Nov 2022 15:09:15 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> So why are you worried about the Org release, and why are you talking
> about fixing bugs after Emacs 29.1 is released? why not fix them while
> Emacs 29.1 is in pretest?
My assumption was that we have to release Org 9.6 _before_ the Emacs
29.1 release cycle begins because the Emacs release branch will be for
bug fixes only and we would not be able to update Org to 9.6 in Emacs
then.
Is it so? Or can we release Org 9.6 _after_ Emacs release branch has
been cut and sync it in this release branch after? (I understand that
sync'ing Org 9.6.1, a bug-fix only release, in the release branch is
fine.)
--
Bastien
next prev parent reply other threads:[~2022-11-16 13:23 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k03vvxs0.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=eliz@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 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.