marsupialSoup has quit [Ping timeout: 264 seconds]
Torr has quit [Quit: Torr]
cmirror has quit [Remote host closed the connection]
cmirror has joined #bitcoin-core-dev
conman has quit [Quit: Konversation terminated!]
bitdex has joined #bitcoin-core-dev
BrandonOdiwuor has quit [Ping timeout: 250 seconds]
willcl-ark has quit [Ping timeout: 255 seconds]
conman has joined #bitcoin-core-dev
willcl-ark has joined #bitcoin-core-dev
willcl-ark has quit [Changing host]
willcl-ark has joined #bitcoin-core-dev
michaelfolkson2 has quit [*.net *.split]
andytoshi has quit [*.net *.split]
Anth0mk- has quit [*.net *.split]
FelixWeis__ has quit [*.net *.split]
jonasschnelli has quit [*.net *.split]
TheCharlatan has quit [*.net *.split]
katsu has quit [*.net *.split]
andytoshi has joined #bitcoin-core-dev
FelixWeis__ has joined #bitcoin-core-dev
michaelfolkson has joined #bitcoin-core-dev
Anth0mk has joined #bitcoin-core-dev
TheCharlatan has joined #bitcoin-core-dev
katsu_ has joined #bitcoin-core-dev
jonasschnelli has joined #bitcoin-core-dev
bitdex has quit [Ping timeout: 260 seconds]
SpellChecker_ has joined #bitcoin-core-dev
Guest20 has joined #bitcoin-core-dev
vasild has quit [Ping timeout: 260 seconds]
SpellChecker has quit [Ping timeout: 260 seconds]
Guest20 has quit [Client Quit]
bitdex has joined #bitcoin-core-dev
vasild has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 272 seconds]
jonatack has joined #bitcoin-core-dev
Guyver2 has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] fjahr opened pull request #30267: assumeutxo: Check snapshot base block is not in invalid chain (master...2024-06-invalid-snapshot-block) https://github.com/bitcoin/bitcoin/pull/30267
JTL has quit [Ping timeout: 268 seconds]
BrandonOdiwuor has joined #bitcoin-core-dev
katsu_ is now known as katsu
JTL has joined #bitcoin-core-dev
dermoth_ has joined #bitcoin-core-dev
dermoth has quit [Remote host closed the connection]
<willcl-ark>
The policy looks good to me, thanks darosior! No comments on the policy itself, but regarding the discussion about EOL not being that clear to users; have we discussed before including EOL dates in debug.log, or in the case of the GUI perhaps even a popup/alert type thing? Obviously we will never push auto-updates, but alerting users that a release-process-released version is/is
<willcl-ark>
approaching EOL could be helpful at drawing more attention to it and prompting users who otherwise might forget, to upgrade.
<sipa>
because at any point a critical vulnerability in 27.0 e.g. could be discovered, leading to the release of 27.1; that does not mean anything became EOL, but you may still need to upgrade
<willcl-ark>
sipa: I understand that, and I'm certainly not suggesting any alert-style "Your software is EOL" or "critical bug, upgrade now!" messaging system :) Nor that this could replace alerting users via conventional channels that they should upgrade due to a critial bug (or similar)
<willcl-ark>
Rather, if we know from the release date of v25(.0) in May 2023 that this branch (and all 25.x releases) will reach maintenance end in 12 months, and EOL say 12 months after that, i.e. May 2025, then this date _could_ be hardcoded into the 25.x releases and display a reminder to the user that their software is reaching/has reached EOL.
<_aj_>
willcl-ark: ie, at branch-off 25.x gets a generic 'EOL_ESTIMATE' set for +20 months away, at which point a warning is added "software is likely no longer supported, consider upgrading to new major version" ? without any corresponding "hey your software is definitely still fine" assertion prior to that...
<_aj_>
willcl-ark: feel a bit like it misses the point that if you're not updating from 25.0 to 25.1 you're not getting any benefit from 25.x not being EOL though
Zenton has quit [Remote host closed the connection]
SpellChecker has quit [Remote host closed the connection]
SpellChecker has joined #bitcoin-core-dev
lbia has joined #bitcoin-core-dev
<achow101>
willcl-ark: I think it would be a bit confusing to do that
<achow101>
We definitely should add standard text to the release notes that says what version is going EOL with that release being made
<achow101>
I think that actually would be enough for preannouncement - the standard text could say, e.g. "As of this release, X.y is now EOL. Any medium and high severity vulnerabilities will be disclosed in 2 weeks"
Robotico has joined #bitcoin-core-dev
Robotico has quit [Remote host closed the connection]
preimage is now known as lattice
jonatack has joined #bitcoin-core-dev
marsupialSoup has quit [Ping timeout: 260 seconds]
Talkless has joined #bitcoin-core-dev
marsupialSoup has joined #bitcoin-core-dev
marsupialSoup has quit [Ping timeout: 260 seconds]
<Murch[m]>
darosior: The disclosure policy looks reasonable to me, looking forward to reading the disclosures. Thanks for working on that
marsupialSoup has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 255 seconds]
jonatack has joined #bitcoin-core-dev
brunoerg has joined #bitcoin-core-dev
jonatack has quit [Ping timeout: 264 seconds]
jonatack has joined #bitcoin-core-dev
marsupialSoup has quit [Ping timeout: 255 seconds]
marsupialSoup has joined #bitcoin-core-dev
___nick___ has joined #bitcoin-core-dev
___nick___ has quit [Client Quit]
___nick___ has joined #bitcoin-core-dev
puchka has joined #bitcoin-core-dev
Talkless has quit [Remote host closed the connection]