Max Nikulin <maniku...@gmail.com> writes:
> New calling convention for `encode-time' exists since emacs-27.1, so it is > incompatible with yet supported emacs-26. It is unfortunate that sources in > Org > and in Emacs repository diverged, but I am unsure if it reasonable to > introduce > a new compatibility wrapper. Emacs developer may be unhappy if the change will > be reverted to way deprecated way to call `encode-time'. For almost a year I > am > reading messages here that Emacs-28 is about to be released, so Emacs-26 is > almost unsupported in Org. > I don' think that is correct. The policy is to support the previous 2 major versions, which means when Emacs 28 is released, org will need to support both 27.x and 26.x. It will likely be necessary to have a compatibility layer for 26.x given the changes.
