From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id wHQEF60a1V6KAgAA0tVLHw (envelope-from ) for ; Mon, 01 Jun 2020 15:11:41 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id kEPnEq0a1V7CfQAAB5/wlQ (envelope-from ) for ; Mon, 01 Jun 2020 15:11:41 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 8F1EA940AD3 for ; Mon, 1 Jun 2020 15:11:40 +0000 (UTC) Received: from localhost ([::1]:46728 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jfm6E-0007KO-MM for larch@yhetil.org; Mon, 01 Jun 2020 11:11:38 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:43496) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jfm5o-0007KI-QY for emacs-orgmode@gnu.org; Mon, 01 Jun 2020 11:11:12 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:50706) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jfm5o-0004YK-6Z; Mon, 01 Jun 2020 11:11:12 -0400 Received: from [2a01:e35:2fe1:f780:a886:3d11:7807:868b] (port=38630 helo=guerry) by fencepost.gnu.org with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.82) (envelope-from ) id 1jfm5n-0004uS-TH; Mon, 01 Jun 2020 11:11:11 -0400 Received: by guerry (Postfix, from userid 1000) id 685771A603C1; Mon, 1 Jun 2020 17:11:10 +0200 (CEST) From: Bastien To: Adam Porter Subject: Re: Policy proposal: Do not move existing functions/macros except in major version increments Organization: GNU References: <87blnqx3ev.fsf@alphapapa.net> Date: Mon, 01 Jun 2020 17:11:10 +0200 Message-ID: <87eeqyes8h.fsf@bzg.fr> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.91 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: emacs-orgmode@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -1.01 X-TUID: cCbyil9O4qCo Hi Adam, Adam Porter 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. > > https://lists.gnu.org/archive/html/emacs-orgmode/2020-04/msg00260.html > https://lists.gnu.org/archive/html/emacs-orgmode/2020-04/msg00259.html > https://lists.gnu.org/archive/html/emacs-orgmode/2020-04/msg00261.html ahem, my bad. I made this bold (and wrong) move, and I broke code out of org-mode. 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: https://updates.orgmode.org/feed/changes Or check the data directly: https://updates.orgmode.org/data/changes 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: https://orgmode.org/Changes.html I think that's a tiny distributed effort for developers and a easy way to track changes for third-party developers. Best, -- Bastien