zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: dana <dana@dana.is>, Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Plan for the 5.9 branch
Date: Wed, 19 Feb 2020 07:21:58 -0800	[thread overview]
Message-ID: <CAH+w=7bYXpzny-eLj2-p+HSZ+0W=fu4-QP3xdYh5wxhq4MMarw@mail.gmail.com> (raw)
In-Reply-To: <20200219103205.0aa6f13f@tarpaulin>

On Wed, Feb 19, 2020 at 2:32 AM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> Now, suppose we add a new feature in March, then in April make
> a release off master that ships that feature, and then in May we find
> a bug in that feature.  Are we allowed to break compatibility with the
> the April version of the feature in order to fix the bug?

If it's a bug such that the feature does not function usably in some
circumstances, or causes a crash, compatibility isn't an issue.

If it's a behavioral difference where the feature does something
usable/useful but inconsistent with the intended behavior, then the
compatibility question arises.  The longer the feature has been "in
the wild" the more likely we are to need to keep compatibility.  For
two months I wouldn't be especially concerned; two years and it
becomes serious.

I can't think of a better approach than to poll a few user channels
(zsh-users, /r/zsh, whatever) to get a feel for how many people are
depending on the anomalous behavior and whether the repair would be
preferable.  Other considerations are how easy it is to make a
run-time decision about which behavior is present (testing a version
number is not an "easy" test in this situation).

  reply	other threads:[~2020-02-19 15:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-16 11:15 Daniel Shahaf
2020-02-16 14:52 ` Peter Stephenson
2020-02-17  2:47 ` dana
2020-02-17  9:19   ` Daniel Shahaf
2020-02-18 19:40     ` dana
2020-02-18 20:44       ` Bart Schaefer
2020-02-19 10:23       ` Daniel Shahaf
2020-02-19 10:32       ` Daniel Shahaf
2020-02-19 15:21         ` Bart Schaefer [this message]
2020-02-19 20:00           ` dana
2020-03-07 22:07 ` Daniel Shahaf

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

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

  git send-email \
    --in-reply-to='CAH+w=7bYXpzny-eLj2-p+HSZ+0W=fu4-QP3xdYh5wxhq4MMarw@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=dana@dana.is \
    --cc=zsh-workers@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).