Hi Bastien, all you wrote is fine IMO. However, I think Ihor's point was mainly in response to the request that we notify the list when compatibility is going to be lost and that when it comes to versions less than the currently maintained versions, this isn't really possible.
To put it in more concrete terms, based on your example below, we don't know exactly when org loses compatibility with Emacs 25.x because we are no longer testing against that version (we are only testing against 28, 27 and 26). We don't know the precise commit which breaks compatibility with 25 as we are no longer testing against that version, so cannot notify the list when compatibility is lost. Obviously, when we do know, we can notify the list. Sometimes, it is clear that a patch or commit will break compatibility with an old version. However, we cannot provide any guarantee we will always notify the list when that compatibility is lost. Often, this only becomes known when someone posts to the list to say it no longer works. Therefore, I think the position should be that once an emacs version is no longer one of the supported versions (current stable Emacs release plus two previous major versions), there is no guarantee we will inform the list when compatibility is lost. If you are running an unsupported versions, either you should avoid updates or be prepared for breakage without warning. When we do know a commit has broken compatibility, that information will be relayed to the list, but we cannot guarantee we can provide such information at the time the change is committed. Running an unsupported versions is at your own risk. Bastien <b...@gnu.org> writes: > Hi Ihor, > > Ihor Radchenko <yanta...@gmail.com> writes: > >> Could you please elaborate on how exactly we can determine if a >> commit changes the compatibility status? > > Today, we are interested in knowing whether Org is compatible with > Emacs 28.1, Emacs 27.1 and Emacs Emacs 26.1. > > Ideally, this means maintainers run the test suite against these > versions in order to check that bugfixes and/or new features don't > introduce incompatible code. > > We don't need to run tests against Emacs <=25: if Org runs okay on > Emacs <=25, it's good. If not, users can report it: maintainers are > not bound to fix such incompatibilities and we don't need to know or > to announce them beforehand since we don't make a promise that Org > will run with Emacs <=25. > > On https://orgmode.org/worg/org-maintenance.html I added this: > > It does not mean that Org will not be usable, at least partially, > with older Emacsen: but maintainers are not bound to fix bugs > reported on them. > > WDYT?