Upgrade targeting platform in 2025 #36
Labels
No labels
bug
duplicate
feature
accepted
feature
proposal
help wanted
invalid
performance
question
user-agent/chromium
user-agent/webkit
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#32 Remove CSS Modules
Rubicon/tutu
Reference: Rubicon/tutu#36
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It's understandable to update the targeting platform every year. For 2025, I'd like to make a small change to the upgrading policy. Instead of blindly updating the version numbers, we try to match the ESR (stands for extended support release) or LTS (stands for long term support) versions in two years for the specific platform.
This makes the targeting more reasonable, because the specific version we blindly use may not actually have enough users. LTS versions have users for sure.
My proposal on the updated targeting platform:
Safari does not have LTS - So we try to match the version with updates in recent 3 years.
Related links:
Upgrade targeting platform (2025)to Upgrade targeting platform in 2025