1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <luke@dashjr.org>) id 1R8lD2-0000ro-A0
for bitcoin-development@lists.sourceforge.net;
Wed, 28 Sep 2011 03:53:24 +0000
X-ACL-Warn:
Received: from zinan.dashjr.org ([173.242.112.54])
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1R8lD1-0004yn-CT for bitcoin-development@lists.sourceforge.net;
Wed, 28 Sep 2011 03:53:24 +0000
Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net
[184.4.160.40]) (Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id DE3FF204031;
Wed, 28 Sep 2011 03:53:17 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: Jeff Garzik <jgarzik@exmulti.com>
Date: Tue, 27 Sep 2011 23:53:08 -0400
User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.5; x86_64; ; )
References: <201109261518.37283.luke@dashjr.org>
<CA+8xBpdFpULC9LrG8NUrKqh37V2-jBm+YFTX6RsB=E8XUkDj9g@mail.gmail.com>
In-Reply-To: <CA+8xBpdFpULC9LrG8NUrKqh37V2-jBm+YFTX6RsB=E8XUkDj9g@mail.gmail.com>
X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583
X-PGP-Key-ID: 665FC11DD53E9583
X-PGP-Keyserver: x-hkp://subkeys.pgp.net
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201109272353.10956.luke@dashjr.org>
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1R8lD1-0004yn-CT
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Miscommitted version
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2011 03:53:24 -0000
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.
|
