From: "Luke-Jr" <luke@dashjr.org>
To: Jeff Garzik <jgarzik@exmulti.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Miscommitted version
Date: Tue, 27 Sep 2011 23:53:08 -0400 [thread overview]
Message-ID: <201109272353.10956.luke@dashjr.org> (raw)
In-Reply-To: <CA+8xBpdFpULC9LrG8NUrKqh37V2-jBm+YFTX6RsB=E8XUkDj9g@mail.gmail.com>
On Tuesday, September 27, 2011 11:44:43 PM Jeff Garzik wrote:
> On Mon, Sep 26, 2011 at 3:18 PM, Luke-Jr <luke@dashjr.org> wrote:
> > * 6b8a5ab Bump version to 0.4.1
> >
> > This should be some pre-0.5.0, not 0.4.1 which will be the stable team's
> > first release...
>
> No. Technically speaking this most recent release was 0.4.0. That is
> what is serialized in the build, and what is tagged.
I'm aware of that.
> Any stable version based off the most recent release would be 0.4.0.1.
Ok. That's not usually how versions work, though. Gavin also recently stated
that the next version after 0.4.0 was to be 0.5, which is why the commit was a
surprise. I'm just trying to clarify what version number to use for stable,
and getting apparently mixed answers.
> And of course you're following the "upstream must have merged this fix
> first" rule, right?
Yep.
prev parent reply other threads:[~2011-09-28 3:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 19:18 [Bitcoin-development] Miscommitted version Luke-Jr
2011-09-28 3:44 ` Jeff Garzik
2011-09-28 3:53 ` Luke-Jr [this message]
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=201109272353.10956.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jgarzik@exmulti.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox