From: dana <dana@dana.is>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh Workers List <zsh-workers@zsh.org>
Subject: Re: Test release: 5.7.1-test-1
Date: Sat, 14 Dec 2019 23:50:38 -0600 [thread overview]
Message-ID: <962BC438-3F7D-41E0-A8BD-9300E5DE1DE8@dana.is> (raw)
In-Reply-To: <20191215051629.ikoezos6bsnirplf@tarpaulin.shahaf.local2>
On 14 Dec 2019, at 23:16, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> I _still_ think -test- tarballs should not describe themselves as the final
> release, but if we have precedent for doing things differently then
> perhaps there's a good reason for that that I'm overlooking.
I don't feel strongly either way. Let's see if anyone else does; if not, i'll
update the instructions according to your preference.
On 14 Dec 2019, at 23:16, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> This implies that the release after ${V}-dev-5 could be either
> ${V}-test-1 or ${V}-test-6, insofar as version number ordering is
> concerned. I don't have a strong preference between these two.
Maybe when you were writing the instructions you interpreted it as resetting
to 1 because we *were* incrementing it, and it just so happens that there's
usually only the one dev release (-dev-0)? If we're going to have it reset i
feel like maybe we should just use 0 for both, but i also don't feel strongly
about resetting vs incrementing. Does anyone else?
On 14 Dec 2019, at 23:16, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> No fault to you for guessing wrongly — on the contrary, kudos for taking
> action and asking on-list afterwards — but I suggest that you revert
> this.
Done. When i update the instructions, i'll make that a 'stable only' step.
dana
next prev parent reply other threads:[~2019-12-15 5:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 19:20 dana
2019-12-15 3:58 ` Daniel Shahaf
2019-12-15 4:32 ` dana
2019-12-15 5:16 ` Daniel Shahaf
2019-12-15 5:50 ` dana [this message]
2019-12-15 18:28 ` Peter Stephenson
2019-12-16 3:55 ` Daniel Shahaf
2019-12-16 22:11 ` dana
2019-12-17 1:16 ` Daniel Shahaf
2019-12-20 21:26 ` dana
2019-12-21 8:13 ` Daniel Shahaf
2019-12-16 1:21 ` 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:
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=962BC438-3F7D-41E0-A8BD-9300E5DE1DE8@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).