From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id 8FK7FRKvlWNAMAEAbAwnHQ (envelope-from ) for ; Sun, 11 Dec 2022 11:21:06 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id +CXrFBKvlWMHUQEAG6o9tA (envelope-from ) for ; Sun, 11 Dec 2022 11:21:06 +0100 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 1DECA10768 for ; Sun, 11 Dec 2022 11:21:05 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p4JRM-0003OI-Q8; Sun, 11 Dec 2022 05:20:12 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p4JRK-0003No-4A for emacs-orgmode@gnu.org; Sun, 11 Dec 2022 05:20:10 -0500 Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p4JRH-0000bS-Pv for emacs-orgmode@gnu.org; Sun, 11 Dec 2022 05:20:09 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id CE11B240026 for ; Sun, 11 Dec 2022 11:20:05 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1670754005; bh=4hcxt/IVyo+EMMxGtcyaepR9HnY3dv/etBBOAOci8gQ=; h=From:To:Cc:Subject:Date:From; b=CFOxY7/WOlq4RDzzLzloDmq0Rsg/N5NG7lTcnjrEIm9NlSmziKdBhjLkzgtqE59aS bAxWIaGFsfJkQdZChOinH4uj5shhWieIznSAY6sLBlu9sEy3rb/Mp37D3nWJeZqdud kBB1Q5T2nWy+E/YCPiFSc8GuDUxqBE67NOgLM1IgCHMRKf0+aCnULOdO4BRZYj713h OvvHYXC3yF3CPKXPkgfQ5OgaYLYYx9VUkUD15s7I/jPsOLsD5S6PFGUupgiDGIKPYg 7Zt0yXplNHsFRJtxEQ2TaXi8VEB4c63K6ik3bG/kiLd5yKITLaQ1k/lmJ0/UHBbLZG aGkAoVqsuk7sA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4NVLNj04h6z6tnQ; Sun, 11 Dec 2022 11:20:05 +0100 (CET) From: Ihor Radchenko To: Tim Cross Cc: Bastien , emacs-orgmode@gnu.org Subject: Re: [MAINTENANCE] Do we have any backwards-compatibility policy for third-party packages? In-Reply-To: <86iljd3x90.fsf@gmail.com> References: <87h6z69myp.fsf@localhost> <86wn7ubflw.fsf@gmail.com> <87cz9lbxdd.fsf@localhost> <86iljd3x90.fsf@gmail.com> Date: Sun, 11 Dec 2022 10:20:02 +0000 Message-ID: <878rjedyy5.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1670754066; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=v+xzw9CyYVhayXn2dXPUkPyP+25/SDY7XmIkYG31cPE=; b=qFQVcJVeq8Z91yiXgZiEZhLBDeuaoVwaVzV6nL8IaILzNACWzF/8JSclfGkOZzoad9b9R+ 65B6bzuczFfrVc7OXFKPPxKBoBU3SofU0/lUVUIf01L6/6mI15Vy2BH2/BkqMetg1ZO1Tu zmD+jzkxDM+rLD+zKmqMnsthmGY8nPMjg6wABYH0oiT7QYhpjilY2rAGyxfDt40CA5RT+p v/ifR0IofKcNgnWLg9WHZGnuYUXjgd9M8pq+lf8uz1w0JH1NfmCgM0KhZNMEsL3dmxMwQd pz0+jMHilqY8+0vjCQ2GAcMtOPJyhBV4E2RJfAEGHgbs8tYIxzBQzOR0lWcroA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b="CFOxY7/W"; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Seal: i=1; s=key1; d=yhetil.org; t=1670754066; a=rsa-sha256; cv=none; b=bOrMS3AEA5UN2NO/DrXe+1yMfRf49YWCaMc0GPkvYFSrAb3dAXBldt7p4s0XnL5u11GuJn UDKiFpKAh0cFpyYfp1u7AfJqE16l96MYduLRUvxPJHxuqUph3z9fZ8CqofOJMkIdSq0ESZ opkMZym36OCfN+J75P7x+X5YJf1Kx4MyMoT8XM4iWpZ6SwFbWkYqUSZDF0KWg5sJ45vmlh poGr8XWxiYucp6E61VCODdsHtbguLyDJjTnDj+p4VTIGuoNqguLoyigmJ6sBZZc2NcMa6H wMWERUYxd01th61rNrv5LyOGzNRUIobBeJPWaNIxBdS4k7DU33XiWsMRlrQXbw== X-Migadu-Spam-Score: -8.23 X-Spam-Score: -8.23 X-Migadu-Queue-Id: 1DECA10768 X-Migadu-Scanner: scn0.migadu.com Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b="CFOxY7/W"; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net X-TUID: 3wYvFD38BEuF Tim Cross writes: > - Adding a section regarding pubic/private API and naming conventions to > the Hacking section of the manual. This section could outline what the > processes are for adding/changing APIs. I think we can add a section to Hacking. But what should we list there? At least, 1. prefix--suffix can change any time. prefix-suffix is stable 2. ORG-NEWS mention if we do important changes breaking (1) 3. If we decide to remove or change some function/variable, we first obsolete it. What else? > - Add the maintainers pledge to the manual as well. It is useful for > users to know what the maintainers pledge to try and do. I doubt many > users will find the page on worg which already exists. At the very > least, add a link to the wrog page. Should we straight put https://bzg.fr/en/the-software-maintainers-pledge/ after Installation section of the manual? Maybe into a new section called "Updating Org"? Bastien, what do you think? > - Briefly document the org maintenance and release process or add links > to relevant worg pages. . Also into Hacking, I think. As extra reference after API and compatibility conventions. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at