zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: "Benjamin R. Haskell" <zsh@benizi.com>
Cc: zsh-workers@zsh.org
Subject: Re: What's the next release number?
Date: Mon, 28 Dec 2015 16:11:15 +0000	[thread overview]
Message-ID: <20151228161115.GK2010@tarsus.local2> (raw)
In-Reply-To: <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
download...

Cheers,

Daniel

> -- 
> Best,
> Ben


  reply	other threads:[~2015-12-28 16:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28 15:02 Daniel Shahaf
2015-12-28 16:07 ` Benjamin R. Haskell
2015-12-28 16:11   ` Daniel Shahaf [this message]
2015-12-28 17:10     ` Benjamin R. Haskell
2015-12-28 17:26 ` Peter Stephenson

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=20151228161115.GK2010@tarsus.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.org \
    --cc=zsh@benizi.com \
    /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).