From: Yuri Khan <yuri.v.khan@gmail.com>
To: Emanuel Berg <moasenwood@zoho.eu>,
help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: [OFFTOPIC] Semver
Date: Tue, 6 Jul 2021 16:28:05 +0700 [thread overview]
Message-ID: <CAP_d_8VeE8=x2X=wUB3SNXTmQKewFScg58x2DQQvSAqLRWZCmQ@mail.gmail.com> (raw)
In-Reply-To: <87zgv0bg9s.fsf@zoho.eu>
On Tue, 6 Jul 2021 at 04:30, Emanuel Berg via Users list for the GNU
Emacs text editor <help-gnu-emacs@gnu.org> wrote:
> >> But what do you do to preserve/break forward compatibility?
> >
> > Strictly speaking, any change to the code can break
> > something somewhere
> > but the general rule to preserve forward compatibility is
> > "don't introduce new features".
> So, new features -> major, drop support -> minor (forward
> OK but not backward), and bugfix -> micro/patch (forward OK,
> backward OK) ?
No, you’ve got it backward.
When we say “version 4.5 is backward-compatible with 4.2”, we mean
“Any software that works correctly with our version 4.2 will also work
correctly with version 4.5”. This means no features were removed that
you’d miss if you upgrade, and no incompatible changes have been
introduced (but some new features may have been added).
When we say “version 4.5.3 is forward-compatible with 4.5.1”, we mean
“Any software that works with 4.5.3 will also work with 4.5.1”. This
means there are no new features in 4.5.3 that you’d miss if you
downgrade (except that you may encounter old bugs).
Bug fixes only: increment patch, compatible both ways.
Feature additions: increment minor, backward compatibility only.
Feature removals: increment major, no compatibility guaranteed.
Dependent software must review changes and integration notes before
upgrading.
next prev parent reply other threads:[~2021-07-06 9:28 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 ` [OFFTOPIC] Semver Stefan Monnier via Users list for the GNU Emacs text editor
2021-07-05 21:30 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06 9:28 ` Yuri Khan [this message]
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='CAP_d_8VeE8=x2X=wUB3SNXTmQKewFScg58x2DQQvSAqLRWZCmQ@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).