Bastien Guerry <b...@gnu.org> writes: > If the current release is de facto compatible with older Emacsen and > a new release will change this, yes, let's announce it in the release > notes. > > We can also send an email to the list using the "X-Woof-Change" to > announce this upcoming change for the upcoming release. > > For example, the current release of Org (9.5.4) is compatible with > Emacs 25.1, as Ihor noted. This is older than Emacs 26. If for some > reason Org 9.6 only supports Emacs >=26, let's announce it on the list > and add an entry in etc/ORG-NEWS and orgmode.org/Changes.html. > > I think doing this manually is fine. > > Bug fixes from the maint branch should never change the compatibility > status of Org.
Could you please elaborate on how exactly we can determine if a commit changes the compatibility status? We can indeed catch some cases by running tests on older Emacs versions, but it is by no means a reliable measure. Also, I just tried to run make EMACS=emacs-25 test, and it fails on bugfix. Yet, Org can be usable on Emacs 25, but not fully. Best, Ihor