📅 Original date posted:2011-07-01
🗒️ Summary of this message: Discussion on the release of Bitcoin version 0.3.24, with debate over whether to cherry-pick specific fixes or release current upstream.
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
My only concern is: How well have the fixes in pull 358 been tested? Wasn't there an issue with the "" account found just last night?
Matt Corallo <bitcoin-list at bluematt.me> wrote:
>Personally, I have little preference, sipa and gmaxwell fall on the
>side
>of cherry-pick, but I think it might be good to do a broad-base test of
>CWallet in 0.3.24 so potential bugs can be found in it before crypto
>and
>0.4. In either case, I dont think we should spend too much time as this
>is just a minor update release, just get it out the door so we can
>focus
>on 0.4 (hopefully) without interruption.
>
>Matt
>
>On Fri, 2011-07-01 at 20:37 -0400, Jeff Garzik wrote:
>> Hum, it sounds like there was some misunderstanding, on my part at
>> least. On IRC, people are talking about a cherry-picked release,
>> basically 0.3.23 + a couple specific fixes, rather than what is
>> current in upstream git. I had assumed people meant releasing
>current
>> git + some specific fixes not yet in git.
>>
>> Wearing the Release Mangler hat, cherry-picked branches have a few
>> disadvantages:
>>
>> * you're throwing away the testing people have done on upstream git
>> * the new branch would have zero testing, as most people have been
>> testing 0.3.23 or upstream git
>> * it would be a dead-end branch, never touched after release. bug
>> reports for such a release might not necessarily be applicable to
>last
>> version or current upstream or anywhere in between.
>>
>> That is the convention wisdom, anyway. But to paraphrase Pirates of
>> the Caribbean, release management rules aren't really rules, they're
>> more like... guidelines. :)
>>
>> The cherry-picked 0.3.24 release, according to IRC wisdom, wouldn't
>> have to worry about shipping CWallet, which needs a fix or two from
>> https://github.com/bitcoin/bitcoin/pull/358
>>
>> I can live with, and roll a release for, either (a) 0.3.23 + select
>> fixes or (b) current upstream + pull #358. My preference is (b), but
>> this is a community and Holy Alpaca decision, not just a call I will
>> make on my own.
>>
>> Comments welcome...
>>
>
>------------------------------------------------------------------------------
>All of the data generated in your IT infrastructure is seriously
>valuable.
>Why? It contains a definitive record of application performance,
>security
>threats, fraudulent activity, and more. Splunk takes this data and
>makes
>sense of it. IT sense. And common sense.
>http://p.sf.net/sfu/splunk-d2d-c2_______________________________________________
>Bitcoin-development mailing list
>Bitcoin-development at lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
- --
Douglas Huff
-----BEGIN PGP SIGNATURE-----
Version: APG v1.0.8
iQIVAwUBTg5uzkPHkQabDWHPAQhEDRAAikf9NX06CSjHOKRdErIEgixHgrcUJk85
GuUxmTIm305WNdxswVDwXhPAqi9PBr5jPYgowp4/UoiYprNHN/s9pPwqNyMI3Urn
SH7rXEA0yYuUU2b2VINY3cxHropu0cGH/EjXOXd+hDf6Dlf/lCsohz3BTcjUho4B
1esBTvhZngmEXaYSs5Hxd7CdbsJ8TVeib8aVGQN3GYc1H4I/MDFNpIsCVB0lAay2
93nczwFvkB/0KyU8vzua8atygdyGNTPWr0BOKvuJO39audokbZmpEREjLiqlIfxj
3MfcUZcOZ9or4Mq8Gq0ZLydpktKSKeZWpbpdzVEk/KQjz+zZhVZ+0jDj4FWIumcS
sd7AdPpQAVVb5uG4ZnALI9V1gmfdXB+yxo7nKdHPCSOTaYwcbHu2+FI7PVlVlh/4
IgcRtZT2p4xoNeuDU+QBinuCDsCPq14f0zPhIo7ZCzs/ruV3Y9BtBS7Ez8FnXIRp
yI06/AX9Bmw2DWBS5Jbu3u32osK1JWBdO9Hh1yVb+O1f9pqDPn7KYroqs4yAPZfx
iz6OaQWtG5Zm+UjoLQiVhPA2cU2Zm42LywtbW3sxm+pmwEx91MeTFCioqOdkz9RI
4NxkaWOlAcXlpr/WX5QoYVcio9GR9AnIeO6h6p4ov0PPI2WqgobrYQbtjdnqxZXi
Q12+wZuYiDo=
=STlK
-----END PGP SIGNATURE-----
Douglas Huff [ARCHIVE] /
npub1xp…c6eq0
2023-06-07 02:00:22
in reply to nevent1q…qxxw
Author Public Key
npub1xpryrka5nmn2vq9uum4qfjcvkfdne95l3ug4sxhdkcnndu4uu6eqrc6eq0Published at
2023-06-07 02:00:22Event JSON
{
"id": "5de2814fa83902eb573ec9ff87d7864b9bd069d84b8ca59bf5556b66192a6104",
"pubkey": "304641dbb49ee6a600bce6ea04cb0cb25b3c969f8f11581aedb62736f2bce6b2",
"created_at": 1686103222,
"kind": 1,
"tags": [
[
"e",
"b259aa9a612285804c8ca826465b76b8809982948e0ab24ccddc1c8a657cc6bd",
"",
"root"
],
[
"e",
"55054c1bd727920ac1cfe7cfd3c960b1e4a43c3b983b62d99ba4be9c72071a05",
"",
"reply"
],
[
"p",
"4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73"
]
],
"content": "📅 Original date posted:2011-07-01\n🗒️ Summary of this message: Discussion on the release of Bitcoin version 0.3.24, with debate over whether to cherry-pick specific fixes or release current upstream.\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\nMy only concern is: How well have the fixes in pull 358 been tested? Wasn't there an issue with the \"\" account found just last night?\n\nMatt Corallo \u003cbitcoin-list at bluematt.me\u003e wrote:\n\n\u003ePersonally, I have little preference, sipa and gmaxwell fall on the\n\u003eside\n\u003eof cherry-pick, but I think it might be good to do a broad-base test of\n\u003eCWallet in 0.3.24 so potential bugs can be found in it before crypto\n\u003eand\n\u003e0.4. In either case, I dont think we should spend too much time as this\n\u003eis just a minor update release, just get it out the door so we can\n\u003efocus\n\u003eon 0.4 (hopefully) without interruption.\n\u003e\n\u003eMatt\n\u003e\n\u003eOn Fri, 2011-07-01 at 20:37 -0400, Jeff Garzik wrote:\n\u003e\u003e Hum, it sounds like there was some misunderstanding, on my part at\n\u003e\u003e least. On IRC, people are talking about a cherry-picked release,\n\u003e\u003e basically 0.3.23 + a couple specific fixes, rather than what is\n\u003e\u003e current in upstream git. I had assumed people meant releasing\n\u003ecurrent\n\u003e\u003e git + some specific fixes not yet in git.\n\u003e\u003e\n\u003e\u003e Wearing the Release Mangler hat, cherry-picked branches have a few\n\u003e\u003e disadvantages:\n\u003e\u003e\n\u003e\u003e * you're throwing away the testing people have done on upstream git\n\u003e\u003e * the new branch would have zero testing, as most people have been\n\u003e\u003e testing 0.3.23 or upstream git\n\u003e\u003e * it would be a dead-end branch, never touched after release. bug\n\u003e\u003e reports for such a release might not necessarily be applicable to\n\u003elast\n\u003e\u003e version or current upstream or anywhere in between.\n\u003e\u003e\n\u003e\u003e That is the convention wisdom, anyway. But to paraphrase Pirates of\n\u003e\u003e the Caribbean, release management rules aren't really rules, they're\n\u003e\u003e more like... guidelines. :)\n\u003e\u003e\n\u003e\u003e The cherry-picked 0.3.24 release, according to IRC wisdom, wouldn't\n\u003e\u003e have to worry about shipping CWallet, which needs a fix or two from\n\u003e\u003e https://github.com/bitcoin/bitcoin/pull/358\n\u003e\u003e\n\u003e\u003e I can live with, and roll a release for, either (a) 0.3.23 + select\n\u003e\u003e fixes or (b) current upstream + pull #358. My preference is (b), but\n\u003e\u003e this is a community and Holy Alpaca decision, not just a call I will\n\u003e\u003e make on my own.\n\u003e\u003e\n\u003e\u003e Comments welcome...\n\u003e\u003e\n\u003e\n\u003e------------------------------------------------------------------------------\n\u003eAll of the data generated in your IT infrastructure is seriously\n\u003evaluable.\n\u003eWhy? It contains a definitive record of application performance,\n\u003esecurity\n\u003ethreats, fraudulent activity, and more. Splunk takes this data and\n\u003emakes\n\u003esense of it. IT sense. And common sense.\n\u003ehttp://p.sf.net/sfu/splunk-d2d-c2_______________________________________________\n\u003eBitcoin-development mailing list\n\u003eBitcoin-development at lists.sourceforge.net\n\u003ehttps://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\n- --\nDouglas Huff\n-----BEGIN PGP SIGNATURE-----\nVersion: APG v1.0.8\n\niQIVAwUBTg5uzkPHkQabDWHPAQhEDRAAikf9NX06CSjHOKRdErIEgixHgrcUJk85\nGuUxmTIm305WNdxswVDwXhPAqi9PBr5jPYgowp4/UoiYprNHN/s9pPwqNyMI3Urn\nSH7rXEA0yYuUU2b2VINY3cxHropu0cGH/EjXOXd+hDf6Dlf/lCsohz3BTcjUho4B\n1esBTvhZngmEXaYSs5Hxd7CdbsJ8TVeib8aVGQN3GYc1H4I/MDFNpIsCVB0lAay2\n93nczwFvkB/0KyU8vzua8atygdyGNTPWr0BOKvuJO39audokbZmpEREjLiqlIfxj\n3MfcUZcOZ9or4Mq8Gq0ZLydpktKSKeZWpbpdzVEk/KQjz+zZhVZ+0jDj4FWIumcS\nsd7AdPpQAVVb5uG4ZnALI9V1gmfdXB+yxo7nKdHPCSOTaYwcbHu2+FI7PVlVlh/4\nIgcRtZT2p4xoNeuDU+QBinuCDsCPq14f0zPhIo7ZCzs/ruV3Y9BtBS7Ez8FnXIRp\nyI06/AX9Bmw2DWBS5Jbu3u32osK1JWBdO9Hh1yVb+O1f9pqDPn7KYroqs4yAPZfx\niz6OaQWtG5Zm+UjoLQiVhPA2cU2Zm42LywtbW3sxm+pmwEx91MeTFCioqOdkz9RI\n4NxkaWOlAcXlpr/WX5QoYVcio9GR9AnIeO6h6p4ov0PPI2WqgobrYQbtjdnqxZXi\nQ12+wZuYiDo=\n=STlK\n-----END PGP SIGNATURE-----",
"sig": "4194ce3358e9ec636a49e486919c6b07d0509c4b9f9a1135aeebb6001349d5ba0dfa028ea29e9d7f4853da155bbbfc395196cda9560325635bc15d632ec6edad"
}