zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: Test release: 5.7.1-test-1
Date: Tue, 17 Dec 2019 01:16:46 +0000	[thread overview]
Message-ID: <20191217011646.cznpheompwvpmwi6@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <D4CBAF2B-9D86-4199-9D05-FD7860B04375@dana.is>

dana wrote on Mon, Dec 16, 2019 at 16:11:13 -0600:
> On 15 Dec 2019, at 21:55, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> > At this point, why don't we change it to X.Y.Z.N-blah
> 
> I like this idea if you guys do. It's easy to understand and should play well
> with just about any version-comparison method. We use a similar scheme where i
> work.
> 
> Pending a decision on that, though...

I'd say, go ahead with making the change unless anyone objects.  It won't
affect the numbering of stable releases so the risk of disruption is minimal.

> On 15 Dec 2019, at 21:55, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> > Please keep whitespace/wrapping changes and substantive changes in separate
> > commits.  They are otherwise hard to review.
> 
> Sorry, that was cheeky. I've broken the white-space changes out into a second
> patch this time

Don't worry about it.

> On 15 Dec 2019, at 21:55, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> > In principle, it'll be nice to have archived copies of all tarballs
> 
> I agree, but it doesn't look like we've done that historically, so i figured
> i'd just document the process we have now. I think i still don't have access
> to zsh.org/pub myself (?), but if i ever get it in the future i can copy the
> artefacts over from Sourceforge and update the instructions going forward

Thanks.  I don't have access either.

Cheers,

Daniel

  reply	other threads:[~2019-12-17  1:17 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
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 [this message]
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=20191217011646.cznpheompwvpmwi6@tarpaulin.shahaf.local2 \
    --to=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).