From: Bastien <firstname.lastname@example.org>
To: Adam Porter <email@example.com>
Subject: Re: Policy proposal: Do not move existing functions/macros except in major version increments
Date: Mon, 01 Jun 2020 17:11:10 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Adam Porter <email@example.com> writes:
> The relatively recent moving of org-get-outline-path to org-refile.el
> has caused breakage in Org itself in several places, e.g.
ahem, my bad. I made this bold (and wrong) move, and I broke code out
I understand your proposal, and it's always good to be reminded that
many people depend on Org's code out there. It is not easy to spend
time working on Org *and* tracking all these interesting extensions.
I agree with Nicolas that we should not put more constraints on the
shoulders of Org current developers, especially because their time is
limited - and obviously not enough to cope with every request.
That said, we can make it easier for third-party developers to know
what changes will be released in the future.
See the "Upcoming changes" in https://updates.orgmode.org
You can subscribe to this RSS feed:
Or check the data directly:
To announce the change you see, I just used this email header:
X-Woof-Change: 9092c289 9.4
That is the commit number where the change happens and the version
in which the change will be released.
The list of upcoming changes is emptied when a new major released is
done, because the changes are then advertized in this file, as usual:
I think that's a tiny distributed effort for developers and a easy
way to track changes for third-party developers.
next prev parent reply other threads:[~2020-06-01 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 2:16 Policy proposal: Do not move existing functions/macros except in major version increments Adam Porter
2020-04-17 9:03 ` Nicolas Goaziou
2020-04-23 3:03 ` Adam Porter
2020-04-23 11:26 ` Nicolas Goaziou
2020-06-01 15:11 ` Bastien [this message]
2020-06-01 18:07 ` Adam Porter
2020-06-01 22:59 ` Bastien
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).