Zsh Mailing List Archive
Messages sorted by:
Re: What's the next release number?
- X-seq: zsh-workers 37443
- From: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
- To: "Benjamin R. Haskell" <zsh@xxxxxxxxxx>
- Subject: Re: What's the next release number?
- Date: Mon, 28 Dec 2015 16:11:15 +0000
- Cc: zsh-workers@xxxxxxx
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=AjyhpgCPxFNXGrGp uP9n8dlUhmc=; b=pcMvXexxIZNQNhLcNK/LRAk75USfr8vVsrLeJJY0qvT6xK+5 0eCSpeUQKvBAw9X3H2pYBt39uiTrPPpy+283s9ZBdbZkYiLQ6JSCHVzyp1Sl88wg bh9AryjP8xDfj/OhDlO55iw5ss+YBVgVEzzxDnC4NUee7K8CI3Ah5QIqNEA=
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=AjyhpgCPxFNXGrG puP9n8dlUhmc=; b=d4q8uZ1tjjHdsywu02g2vSMe/xGTsDFy/lYb64ApanU5qCf K0i9Ewq8jhkvuKdOv6NoHjsPMfWOcbXAk6lXKJe6dmx6zfxlD5jrNNEGz9kyC61Y KF5qjAWWr2ZxlhfZ5OvDRryk9pBCZav2KWv3wKvZTIO0sZbW2xAkQmTDrzIw=
- In-reply-to: <CAB2RFrTWc+TkdJrruRUYZfGNCkfqq-nea3=6svS8Lnn0kHqbJg@mail.gmail.com>
- List-help: <mailto:email@example.com>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:firstname.lastname@example.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20151228150238.GD2010@tarsus.local2> <CAB2RFrTWc+TkdJrruRUYZfGNCkfqq-nea3=6svS8Lnn0kHqbJg@mail.gmail.com>
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".
> 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 specific
> 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
Messages sorted by: