From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: dana <dana@dana.is>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Plan for the 5.9 branch
Date: Wed, 19 Feb 2020 10:32:05 +0000 [thread overview]
Message-ID: <20200219103205.0aa6f13f@tarpaulin> (raw)
In-Reply-To: <EF04BEAA-BBEE-447B-BD8A-9606016D4FA6@dana.is>
dana wrote on Tue, 18 Feb 2020 13:40 -0600:
> On 17 Feb 2020, at 03:19, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> On 17 Feb 2020, at 03:19, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> > What degree of support/compatibility promises will they
> > come with — comparable to a -dev/-test release or to a regular release? Etc.
>
> Re: compatibility, as a rule i would suggest that patch releases under this
> system should not contain anything that Debian/Ubuntu wouldn't be comfortable
> pulling into one of their (non-rolling) releases. Maybe that's slightly too
> strict in practice, but i think that's a reasonable goal at least.
>
> Re: support, i'm not sure i even know what promises we make for stable
> releases now, lol
For one, we implicitly promise compatibility: if something works
in 5.8, users are allowed to assume it will work in 5.9 as well.
(Which by extension means bugs in it will be considered release
blockers)
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 the feature hadn't appeared in a release, the answer would be an
unequivocal "Yes". Given that it has appeared in a release, do we promise
to users of that release that we won't break compatibility with what
they have? If we don't promise that, fewer users will install the
additional releases; but if we do make that promise, we'll have less
time to find bugs in features before we're committed to support those
features going forward.
Cheers,
Daniel
next prev parent reply other threads:[~2020-02-19 10:32 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 [this message]
2020-02-19 15:21 ` Bart Schaefer
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=20200219103205.0aa6f13f@tarpaulin \
--to=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).