unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: [OFFTOPIC] Semver
Date: Wed, 30 Jun 2021 16:00:04 -0400	[thread overview]
Message-ID: <jwvwnqb6sfr.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 87v95v5dzy.fsf@zoho.eu

> But what do you do to preserve/break forward compatibility?

Strictly speaking, any change to the code can break something somewhere
(https://xkcd.com/1172/), but the general rule to preserve forward
compatibility is "don't introduce new features".

You can preserve forward compatibility while breaking backward
compatibility, e.g. by making a release that adds no new features but
drops support for old features (e.g. making the code more efficient
along the way).


        Stefan




  reply	other threads:[~2021-06-30 20:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-26 18:05 Emacs Versions: major, minor and ...? Colin Baxter
2021-06-26 18:27 ` Eli Zaretskii
2021-06-26 19:38   ` Colin Baxter
2021-06-27  5:47     ` Eli Zaretskii
2021-06-28  3:56 ` mrf
2021-06-28  4:22   ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-06-28  5:29     ` Colin Baxter
2021-06-28  5:30     ` mrf
2021-06-28  5:14   ` Colin Baxter
2021-06-29 10:07   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-29 22:11     ` [OFFTOPIC] Semver (was: Emacs Versions: major, minor and ...?) Stefan Monnier via Users list for the GNU Emacs text editor
2021-06-30 19:49       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-30 20:00         ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
2021-07-05 21:30           ` [OFFTOPIC] Semver Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06  9:28             ` Yuri Khan
2021-07-06  9:54               ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06 11:49                 ` Yuri Khan
2021-07-06 16:29                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06 17:00                   ` [External] : " Drew Adams

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvwnqb6sfr.fsf-monnier+emacs@gnu.org \
    --to=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).