Re: The emacs-31 branch during the next release cycle
Stefan Monnier <[email protected]> Fri, 26 Jun 2026 12:01:23 -0400
| Newsgroups | gmane.emacs.devel,gmane.linux.debian.devel.emacsen |
|---|---|
| Message-ID | <[email protected]> |
>> >> From: Stefan Monnier via "Emacs development discussions." <[email protected]> >> [...] >> >> - After NN.1 is released, I expect much fewer people run the `emacs-NN` >> >> branch, so any regression risks remaining undetected before the next >> >> (minor) release. If the regression is detected earlier, it'll likely >> >> be detected by someone running `master` and there's a chance that the >> >> fix will make it only to `master` if we don't notice the link to the >> >> previous bug-fix or don't notice that that previous bug-fix was >> >> installed in `emacs-NN`. >> > >> > The problems for which we install fixes on the release branch after >> > NN.1 release come from 2 sources: >> >> Just to clarify: The paragraph I wrote above talks regressions due to >> new bug-fixes installed on the `emacs-NN` branch, not regressions >> present in NN.1. >> >> Rereading just now made me realize that it wasn't obvious at all. > > No, it wasn't. But anyway, bugs we fix on a release branch aren't > limited to regressions since NN-1.x releases, we also fix bugs in > earlier releases, as long as they are safe to fix. No, no, I'm really talking about regressions introduced by the bug-fix patches installed in `emacs-NN`. IOW about the problems that show up when what we seemed like a "safe bug-fix" isn't. === Stefan