From: Ihor Radchenko <email@example.com>
To: firstname.lastname@example.org, Bastien <email@example.com>
Subject: [MAINTENANCE] Do we have any backwards-compatibility policy for third-party packages?
Date: Fri, 11 Nov 2022 03:41:50 +0000 [thread overview]
Message-ID: <87h6z69myp.fsf@localhost> (raw)
Org promises to support the last three Emacs releases.
However, it is less clear what is our policy wrt third-party packages.
We do need third-party packages, for example, in babel backends.
Sometimes, we have to make changes to the ob-*.el files in order to
accommodate changes in the required third-party packages. Like in recent
changes to ob-scheme where `run-geiser' function is now obsolete
Should we try to support obsolete functions/variables in third-party
packages? Should we try to work around breaking changes and support both
before/after package versions?
The answer is not obvious as older Emacs versions might not be supported
by some third-party packages. Then, logically, we have to support older
package versions compatible with the oldest Emacs version we support.
But it might be hard to keep track of such scenarios.
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next reply other threads:[~2022-11-11 3:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 3:41 Ihor Radchenko [this message]
2022-11-16 22:33 ` [MAINTENANCE] Do we have any backwards-compatibility policy for third-party packages? Tim Cross
2022-11-17 12:04 ` Ihor Radchenko
2022-11-17 23:38 ` Tim Cross
2022-12-10 13:48 ` Ihor Radchenko
2022-12-11 3:24 ` Tim Cross
2022-12-18 12:45 ` Ihor Radchenko
2022-12-11 10:20 ` Ihor Radchenko
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).