Zsh Mailing List Archive
Messages sorted by:
Re: What's the next release number?
- X-seq: zsh-workers 37444
- From: "Benjamin R. Haskell" <zsh@xxxxxxxxxx>
- To: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
- Subject: Re: What's the next release number?
- Date: Mon, 28 Dec 2015 12:10:05 -0500
- Cc: zsh-workers@xxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=benizi-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=+ISei8/dRAeUOCO+1fbs08OoN5GL2GESVFPyWFV2aLs=; b=XGsVXUBR0DVUXrMziy2HryEEWpC2bipPX+B7jeg+z/12I1Eq1A9+5vl1bNstAyVto0 c0x28bb/lTTGXhT+MOhRlhSpp8+0bpjQslVfnCBLL7B9ezH1UPlBqRQfmD97c/pPu1Wi 4A+B7mdtILHngI6lFAYZqNrpvyS/gbLwaFSUm9S7ZbPAUfYoGC8bWJ/WFC3ykPvbkM0s lQEzWyBKnIXQ3xn0J1IMJiSp/59u9R7wJC9Wp9n0x6eJhuDwfnbBa5rl+PCX94yd9jhZ Gs1+e8s3e9k5sd+aByiAw0uE7etge+P9F4tcuo3XyCXzXYBKKnpisXQ9xLD7wc4Vm2OZ lXFw==
- In-reply-to: <20151228161115.GK2010@tarsus.local2>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:email@example.com>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20151228150238.GD2010@tarsus.local2> <CAB2RFrTWc+TkdJrruRUYZfGNCkfqq-nea3=6svS8Lnn0kHqbJg@mail.gmail.com> <20151228161115.GK2010@tarsus.local2>
- Sender: benizi@xxxxxxxxxx
On Mon, Dec 28, 2015 at 11:11 AM, Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
> Benjamin R. Haskell wrote on Mon, Dec 28, 2015 at 11:07:12 -0500:
> > What's an example situation? "The change will appear after version X.Y"
> > and "The bug was fixed after version X.Y" both seem reasonable to me for
> > situations that need a description in natural language.
> In zsh-syntax-highlighting, when I make a bugfix that depends on
> a bugfix in zsh, in the ticket I'd like to say "The fix requires
> zsh 5.1.2 or newer".
"The fix requires zsh newer than 5.1.2"
> For something automated (e.g. `is-at-least X.Y.Z`), you can just assume it
> > will be a patch release, since the version increment will be at least as
> > much as a patch release. Even if no release ever exists with that
> > version, the next release will still compare as greater.
> Sure. But for natural language it might be confusing to refer people to
> "5.1.2 and newer" when there's no zsh-5.1.2.tar.gz available for
Agreed, so for natural language, I think the correct approach is to avoid
trying to specify a future version. Just use "newer than x.y.z"
Messages sorted by: