DevMeeting - 2021-07-26/27 #2055
Replies: 1 comment 2 replies
-
A longer form description of the update to deprecations development practice (originally written #2052 (comment)) We discussed a change to deprecation policy that deprecations on minor versions are now the standard with removal in the subsequent major version. Our reasoning is that this enables better development practice, cleaner code, and more agility. A basic problem we've had for a long time is that we often deprecate and never remove, and sometimes even deprecate things without replacement. The new development flow is that, if an API is to be changed, it is deleted on master and backported to the latest major version. This deletion on master will keep the main codebase cleaner, while also requiring the developer to update all tests thus ensuring we know what the code migration path looks like and that it is appropriate to deprecate the API. The backport will then fail (because it won't be binary compatible), and the developer is then required to deprecate the API on the backport. This has a massive benefit that the internal hacks that are often necessary to maintain some deprecated APIs will only have to be made on the backport branch and will never exist on master. Finally, it's true that people may sometimes skip minor versions. It will become part of our release notes and announcement notes which minor version users need to bump to before bumping to the major release. This requires a bit of additional discipline but I believe the benefits to be worth it. |
Beta Was this translation helpful? Give feedback.
-
2021-07-26/27
Outreach
Updates
Pinned Items
me.jiuyang.cde::cde:0.1
now, when those PRs merged, I’ll remove my fork.Discussion 1
Discussion 2
Beta Was this translation helpful? Give feedback.
All reactions