Luke-Jr [ARCHIVE] on Nostr: 📅 Original date posted:2013-05-25 📝 Original message:On Saturday, May 25, 2013 ...
📅 Original date posted:2013-05-25
📝 Original message:On Saturday, May 25, 2013 8:25:35 AM Melvin Carvalho wrote:
> It might be an idea to have 'rule change' fixes and 'bug fix' releases go
> out separately
Bitcoin is a consensus system. You can't run clients with different rules on
the same blockchain/network - it just won't work! Maybe we're now talking
about mere client default policies? In which case, you should be able to
configure previous behaviour...
If you want just bug fixes and rule changes, without policy default changes,
new features, etc, you can use the 0.4.x - 0.7.x backports. But be advised
these are short-term solutions and won't be maintained forever - so you really
should try to get the behaviour you want from the current release. If you
can't for some reason, please do report a bug explaining what it is the older
version was capable of that the new one isn't!
Luke
Published at
2023-06-07 15:02:27Event JSON
{
"id": "3e9d90929b90c3cae034860baaf4c0c4227d00cea1a3df584c0f35854b54f6e1",
"pubkey": "6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1",
"created_at": 1686150147,
"kind": 1,
"tags": [
[
"e",
"2e4ed8621239305d3661a7f5128ae289da4cef55f854def90b39bf0c1366d978",
"",
"root"
],
[
"e",
"cb679cbff3ff7ba2e606dfec84419a03f61245f0766a15552c682effad79e582",
"",
"reply"
],
[
"p",
"e316966328c4cb66c34719ef9a7b3bc54ef601663ad4ab06185991237735aa19"
]
],
"content": "📅 Original date posted:2013-05-25\n📝 Original message:On Saturday, May 25, 2013 8:25:35 AM Melvin Carvalho wrote:\n\u003e It might be an idea to have 'rule change' fixes and 'bug fix' releases go\n\u003e out separately\n\nBitcoin is a consensus system. You can't run clients with different rules on \nthe same blockchain/network - it just won't work! Maybe we're now talking \nabout mere client default policies? In which case, you should be able to \nconfigure previous behaviour...\n\nIf you want just bug fixes and rule changes, without policy default changes, \nnew features, etc, you can use the 0.4.x - 0.7.x backports. But be advised \nthese are short-term solutions and won't be maintained forever - so you really \nshould try to get the behaviour you want from the current release. If you \ncan't for some reason, please do report a bug explaining what it is the older \nversion was capable of that the new one isn't!\n\nLuke",
"sig": "bddd6edb61bb5c902a8f2c96f5a60db95a2f0bb53548443952087ad68aaeca94227440ed183e8ef4e41a85b3347aa41731a18dcaff42a07ef306f8db887639cc"
}