Closed fanquake closed 3 weeks ago
I've used .x
because that is what we currently use for branches: https://github.com/bitcoin/bitcoin/branches.
Yes, but the website documentation is meant for users of the software, not developers of the software. I don't feel strongly though of course.
~
Concept ACK.
lgtm. If you are open to more bikeshedding, could add something like "Only the last point release of each supported major release version will have the latest security fixes." before the sentence "Once EOL is reached, you will need to upgrade to a newer version"? But either way, this looks good.
Merging, main point is to remove eol 24. Sounds like we will have more opportunities to make lifecycle info clearer in the near future
"Only the last point release of each supported major release version will have the latest security fixes."
I'm not sure this wouldn't mislead users into believing minor releases would always have the latest security fixes, which we unfortunately can't guarantee. On Wednesday, June 12th, 2024 at 4:08 PM, maflcko @.***> wrote:
lgtm. If you are open to more bikeshedding, could add something like "Only the last point release of each supported major release version will have the latest security fixes." before the sentence "Once EOL is reached, you will need to upgrade to a newer version"? But either way, this looks good.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>
Using
.x
should make it clearer that it is the branch that is maintained. In particular, the most-recent point release on the branch.