From: "Benjamin R. Haskell" <zsh@benizi.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Subject: Re: What's the next release number?
Date: Mon, 28 Dec 2015 11:07:12 -0500 [thread overview]
Message-ID: <CAB2RFrTWc+TkdJrruRUYZfGNCkfqq-nea3=6svS8Lnn0kHqbJg@mail.gmail.com> (raw)
In-Reply-To: <20151228150238.GD2010@tarsus.local2>
[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]
On Mon, Dec 28, 2015 at 10:02 AM, Daniel Shahaf <d.s@daniel.shahaf.name>
wrote:
> How can I now, at a given point in time, what will be the next release's
> version number?
>
You can't know. It depends on how significant a release it is.
I keep running into situations where I need to refer to a change made in
> master using the release number it's expected to first appear in, and
when I try to guess what that number will be, I get it wrong. (E.g.,
> when 5.0.8 was current I wrote "The change will appear in 5.0.9" and
> there is no such version. Ditto for 5.1.2/5.2.)
> I could say "the change will appear in the release after 5.2", but
> that's needlessly complicated: I'd much rather be able to say "The
> change will appear in release ${foo}" for one specific value of ${foo}.
>
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.
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.
--
Best,
Ben
next prev parent reply other threads:[~2015-12-28 16:07 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 [this message]
2015-12-28 16:11 ` Daniel Shahaf
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='CAB2RFrTWc+TkdJrruRUYZfGNCkfqq-nea3=6svS8Lnn0kHqbJg@mail.gmail.com' \
--to=zsh@benizi.com \
--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).