From: dana <dana@dana.is>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Plan for the 5.9 branch
Date: Tue, 18 Feb 2020 13:40:29 -0600 [thread overview]
Message-ID: <EF04BEAA-BBEE-447B-BD8A-9606016D4FA6@dana.is> (raw)
In-Reply-To: <20200217091958.0fa9f1d8@tarpaulin.shahaf.local2>
On 17 Feb 2020, at 03:19, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> I think even before documenting the process, we'll have to agree on
> what the goal is and what the additional releases would contain. Just bugfixes,
> or also new features?
Right. All i'm really worried about personally are fixes for security issues
and the type of regressions we normally correct in .1 releases.
Beyond that, maybe stuff like trivial completion updates could go in if we're
planning a patch release anyway — that's what we've done lately with .1
releases — but i don't think it's important and i'm not suggesting that we go
out of our way for them.
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
dana
next prev parent reply other threads:[~2020-02-18 19:41 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 [this message]
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
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=EF04BEAA-BBEE-447B-BD8A-9606016D4FA6@dana.is \
--to=dana@dana.is \
--cc=d.s@daniel.shahaf.name \
--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).