📅 Original date posted:2015-10-01
📝 Original message:On Wed, Sep 30, 2015 at 05:57:42PM +0000, Luke Dashjr wrote:
> On Thursday, September 24, 2015 11:25:56 AM Wladimir J. van der Laan via
> bitcoin-dev wrote:
> > 2015-12-01
> > -----------
> > - Feature freeze
>
> Where is "Consensus freeze"? Shouldn't this be put off until after the HK
> workshop in case a hardfork is decided on? Or have we de-coupled it from the
> release process entirely anyway (since old versions need an update for it
> too)?
In principle, "feature freeze" means that any large code changes will no longer go into 0.12, unless fixing critical bugs.
I'm not keen on postponing 0.12 for such reasons - after the HK workshop I'm sure that it will take some development/testing/review before code makes it into anything. Apart from that there's a good point to decouple consensus changes from Bitcoin Core major releases.
We've seen lot of release date drift due to "this and this change needs to make it in" in the past, that was a major reason to switch to a time-based instead of feature-based release schedule.
We can always do a 0.12.1.
Wladimir
Wladimir J. van der Laan [ARCHIVE] /
npub1ts…rfl5y
2023-06-07 17:42:12
in reply to nevent1q…qyjp
Author Public Key
npub1ts9hljj3l4yrpdxelpqdup3l46lw40fmkhw3rr0feh6s5ml247vqerfl5yPublished at
2023-06-07 17:42:12Event JSON
{
"id": "8b88328af7d320f4c20ef1f103f3a4efcbec198d1ea3e60f17b1819f3764663c",
"pubkey": "5c0b7fca51fd4830b4d9f840de063faebeeabd3bb5dd118de9cdf50a6feaaf98",
"created_at": 1686159732,
"kind": 1,
"tags": [
[
"e",
"fe21d0d1bd47c033c20b54283ababb012de793c76cc31b322bb55ff5ed527268",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2015-10-01\n📝 Original message:On Wed, Sep 30, 2015 at 05:57:42PM +0000, Luke Dashjr wrote:\n\u003e On Thursday, September 24, 2015 11:25:56 AM Wladimir J. van der Laan via \n\u003e bitcoin-dev wrote:\n\u003e \u003e 2015-12-01\n\u003e \u003e -----------\n\u003e \u003e - Feature freeze\n\u003e \n\u003e Where is \"Consensus freeze\"? Shouldn't this be put off until after the HK \n\u003e workshop in case a hardfork is decided on? Or have we de-coupled it from the \n\u003e release process entirely anyway (since old versions need an update for it \n\u003e too)?\n\nIn principle, \"feature freeze\" means that any large code changes will no longer go into 0.12, unless fixing critical bugs. \n\nI'm not keen on postponing 0.12 for such reasons - after the HK workshop I'm sure that it will take some development/testing/review before code makes it into anything. Apart from that there's a good point to decouple consensus changes from Bitcoin Core major releases.\n\nWe've seen lot of release date drift due to \"this and this change needs to make it in\" in the past, that was a major reason to switch to a time-based instead of feature-based release schedule.\n\nWe can always do a 0.12.1.\n\nWladimir",
"sig": "caadd3801b1c5bc243d593f134eb8b6d12afe39128d9208c7d3fdfea962b8cd826632def648a54f59329d1b0855c857050a6ff5323a3e01dc6bec4c55133d8ea"
}