📅 Original date posted:2014-06-13
📝 Original message:On Friday, 13 June 2014, at 9:24 pm, xor wrote:
> On Friday, June 13, 2014 12:18:37 PM Wladimir wrote:
> > If I do not hear anything, I will do a
> > last-minute language import
>
> High risk projects as Bitcoin should NOT see ANY changes between release
> candidates and releases.
>
> You can cause severe havoc with ANY changes. Humans make mistakes!
> Please do not do such things!
Agreed. Does Bitcoin Core not have a release cycle policy? Typically mission-critical projects will enter a code and resource freeze prior to tagging a release candidate, after which point only critical bugfixes are allowed into the release branch. A language translation update does not qualify as a critical bugfix and should be merged during the next release cycle.
Matt Whitlock [ARCHIVE] /
npub17q…upwet
2023-06-07 15:22:38
in reply to nevent1q…nwmm
Author Public Key
npub17qxssk9sj2r7jswvh3y32e7vwz7mcckhz33gk9nurdmw0lhsfkgswupwetSeen on
wss://relay.nostr.bandPublished at
2023-06-07 15:22:38Event JSON
{
"id": "b1ac15fc0164493e5199751c13e28783458b94cb094a33f87a9f6a820309602c",
"pubkey": "f00d0858b09287e941ccbc491567cc70bdbc62d714628b167c1b76e7fef04d91",
"created_at": 1686151358,
"kind": 1,
"tags": [
[
"e",
"a7227de8a6e97c1dbd351d4724658eec4042be0f772d051e197a562ef93f0d92",
"",
"root"
],
[
"e",
"be24945744794bd484996fd3ca54506cd4d76d237dc583e3e92187d9ae3e0f09",
"",
"reply"
],
[
"p",
"af7cc88ea10a48f7fa0f5d9577f25789ee53557a910736e58506f7d1354c1c18"
]
],
"content": "📅 Original date posted:2014-06-13\n📝 Original message:On Friday, 13 June 2014, at 9:24 pm, xor wrote:\n\u003e On Friday, June 13, 2014 12:18:37 PM Wladimir wrote:\n\u003e \u003e If I do not hear anything, I will do a\n\u003e \u003e last-minute language import\n\u003e \n\u003e High risk projects as Bitcoin should NOT see ANY changes between release\n\u003e candidates and releases.\n\u003e \n\u003e You can cause severe havoc with ANY changes. Humans make mistakes!\n\u003e Please do not do such things!\n\nAgreed. Does Bitcoin Core not have a release cycle policy? Typically mission-critical projects will enter a code and resource freeze prior to tagging a release candidate, after which point only critical bugfixes are allowed into the release branch. A language translation update does not qualify as a critical bugfix and should be merged during the next release cycle.",
"sig": "aae5162ff6fa799d47df524ec931400cf6de418ee99f778ba2e3f5e7fc319b7cd8829d6e6209f4e4a5db330fcb355f4fbd9e1e09e93ede9673a05986e244460d"
}