help / color / mirror / code / Atom feed
From: dana <dana@dana.is>
To: "Zsh hackers list" <zsh-workers@zsh.org>
Subject: Re: We should get 5.9** out soon
Date: Sat, 02 Apr 2022 17:42:40 -0500	[thread overview]
Message-ID: <bc8a9d2f-013e-4874-8a40-820876df2ac0@www.fastmail.com> (raw)
In-Reply-To: <17292100-61f9-4183-8d04-6f8443f3c2f7@www.fastmail.com>

I hope to post a test release within the next week. I need to go through
the recent activity myself and do a few documentation updates, and Mikael
suggested that i might also wait for Bart's patch from w/49955 to go in.
If anyone else wants anything in for testing, please try to get it done

Re: 5.9 vs 6.0, based on the discussion here and on IRC it seems like we
have two strong 5.9s (Daniel and Axel), one weak 5.9 (Matthew), and two
weak 6.0s (pws and Bart). Mikael and i are indifferent. Please let me
know if i've misinterpreted anyone's position. If not, i think the 5.9s
have it so far.

PS: There has been some discussion in the past about changing the release
process so that instead of going directly off master we e.g. make a 5.9
branch as the 'cycle' is winding down and release off that. Since we
never settled on any of those process changes my current plan is to just
release off master like usual, but let me know if anyone feels
differently about that too.


  reply	other threads:[~2022-04-02 22:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 16:51 Bart Schaefer
2022-03-31  0:34 ` dana
2022-03-31  0:48   ` Bart Schaefer
2022-03-31 10:23   ` Peter Stephenson
2022-03-31 10:47   ` Daniel Shahaf
2022-03-31 10:54     ` Axel Beckert
2022-03-31 11:05     ` Peter Stephenson
2022-03-31 23:31       ` Daniel Shahaf
2022-04-02 22:42         ` dana [this message]
2022-04-03 16:07           ` Peter Stephenson
2022-04-03 16:39           ` Bart Schaefer
2022-04-03 17:04           ` Branching (was Re: We should get 5.9** out soon) Bart Schaefer
2022-04-03 19:34             ` dana

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:

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

  git send-email \
    --in-reply-to=bc8a9d2f-013e-4874-8a40-820876df2ac0@www.fastmail.com \
    --to=dana@dana.is \
    --cc=zsh-workers@zsh.org \


* 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


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).