New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: add disclaimer to release timeline #40717
Conversation
160ac03
to
ff95651
Compare
ff95651
to
565fdb0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion: We put any dates which are subject to change in the table in italics with an asterisk at the end, to help provide more of a visual cue.
The disclaimer feels like it's just repeating the information that already exists below, I'm tempted to cut it to just the blurb that says dates are subject to change due to upstream.
Co-authored-by: David Sanders <dsanders11@ucsbalum.com>
No Release Notes |
I have automatically backported this PR to "28-x-y", please check out #40884 |
I have automatically backported this PR to "29-x-y", please check out #40885 |
Description of Change
Follow up to #40622 - we caught a change in Chromium's schedule fairly late in the game, and updated the timeline doc after apps may have set their own schedules depending on the previous EOL date.
While we should always make sure this table is accurate, this PR adds a disclaimer to the timeline to clarify that the last 3 stable versions are supported, and how dates are determined.
Checklist
npm test
passesRelease Notes
Notes: none