From: Tim Cross <firstname.lastname@example.org> To: email@example.com Subject: Re: [PATCH] Fix window width when line numbers present Date: Tue, 23 Nov 2021 18:05:10 +1100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Bastien <firstname.lastname@example.org> writes: > Hi Ihor, > > Ihor Radchenko <email@example.com> writes: > >> The text is mostly clear. However, there is a slight confusion about >> actual current Emacs version vs. planned Emacs version. > > I've rephrased it a bit to focus on "releases", not "versions": > > We aim at keeping the latest stable version of Org compatible with > the *last three major releases of Emacs*. > > For example, if the latest release of Emacs is 28.x, then you can > assume that the latest release of Org is compatible with Emacs 28.x, > 27.x and 26.x, but not with Emacs 25.x. > >> Should we target "current" Emacs 28 for main? Should we target Emacs >> version+1 as current on main all the time or maybe just when new >> Emacs release branch is created, but not yet released? It is not >> fully clear. > > These paragraphes on Worg try to explicit reasonable expectations > for users and are thus focusing on stable releases only. > > Expectactions for development versions are another story: I am in > favor of not trying to commit to _any_ expectactions for Org's main. > > For example, I would not mind a feature on main that relies on a new > feature in the Emacs development branch, as long as we manage to keep > the promise that the next Org stable is usable with the older Emacs > releases. So what your saying is that if the current main branch relies on a new feature in the current Emacs development branch, then org must also have a compatibility function so that the feature works with at least the last 2 released versions (possibly 3 since we don't know when the new Emacs version will be released and we may need/want to release main before the new Emacs version is released). So basically, if you want to use a new feature in development Emacs, you will also need to implement a compatibility version for the previous 2 or 3 Emacs versions. This probably sounds worse than it is in practice because most of the time, once you have a compatibility implementation for the previous version, it will likely work with the previous 2 or 3 versions. It further means that a new feature added into Emacs cannot be used in org without a compatibility version until it has been in Emacs for 3 versions.
next prev parent reply other threads:[~2021-11-23 7:15 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-21 18:41 Matt Huszagh 2021-11-21 19:14 ` Timothy 2021-11-21 21:08 ` Nicolas Goaziou 2021-11-21 21:14 ` Matt Huszagh 2021-11-21 21:16 ` Bastien 2021-11-21 21:22 ` Matt Huszagh 2021-11-22 5:14 ` Bastien 2021-11-22 5:31 ` Timothy 2021-11-22 5:44 ` Bastien 2021-11-22 5:51 ` Supported Emacs version (was: [PATCH] Fix window width when line numbers present) Timothy 2021-11-22 6:05 ` Supported Emacs version Bastien 2021-11-22 6:12 ` Timothy 2021-11-22 6:39 ` Bastien 2021-11-22 8:04 ` Timothy 2021-11-22 10:26 ` Bastien 2021-11-22 11:55 ` [PATCH] Fix window width when line numbers present Ihor Radchenko 2021-11-22 12:40 ` Tim Cross 2021-11-23 5:59 ` Bastien 2021-11-23 7:05 ` Tim Cross [this message] 2021-11-22 3:16 ` Timothy 2021-11-21 19:19 ` Timothy
Reply instructions: 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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] Fix window width when line numbers present' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git 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).