> From: Bastien <bzg@gnu.org> > Cc: larsi@gnus.org, emacs-devel@gnu.org, yantar92@gmail.com, > kyle@kyleam.com > Date: Wed, 16 Nov 2022 14:23:11 +0100 > > 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. I see no reason to require the emacs-29 branch to have a released version of Org in it. From the Emacs POV, what matters is that you don't add new features to Org that is part of the branch after the branching point. Other than that, you can make the official Org 9.6 release whenever you want, as long as what will be on master immediately before the branching point is close enough to 9.6, such that only minor changes (and bugfixes) will be needed there before Emacs 29.1 is released. > 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? This is undesirable if what we have now on master is very different from 9.6. If it is not very different, you are free to release Org 9.6 whenever you want.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4