Skip to content

Commit 1438476

Browse files
authored
Update deprecation policy (#151257)
We are pausing our cadence of removing deprecated API from the framework until we can create a new policy. The last couple of cycles we noticed customers having more difficult migrations, and it being harder to remove the APIs in the scheduled time period. So we need to reevaluate the policy and update it. This is the policy working as intended. Signals like flutter/tests provide feedback on how we are affecting users - so that for folks that contributed! Related to flutter/website#10839
1 parent d1e1500 commit 1438476

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

docs/contributing/Tree-hygiene.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -458,9 +458,10 @@ When adding a deprecation notice to the framework, a flutter fix should be inclu
458458

459459
When deprecating features, be aware that *you* will not by default be informed when the Flutter code itself uses the deprecated feature (there is a `deprecated_member_use_from_same_package: ignore` line in the root `analysis_options.yaml` file). To find places where the old feature is used, rename its declaration and see where the compiler complains. (You can't just comment out the "ignore" in the `analysis_options.yaml` file because it's hiding hundreds of other warnings...)
460460

461-
Deprecations are removed in a consistent "first-in-first-out" fashion. The lifetime for a Flutter deprecation is 1 year after reaching the stable channel, or after 4 stable releases, whichever is longer. Deprecations are still subject to the policy described on the [breaking changes page](https://flutter.dev/docs/release/breaking-changes) of the website. Where possible, prepare the dart fix tools and write appropriate migrations guides.
462-
463-
This policy is currently enforced for `package:flutter`, `package:flutter_driver`, and `package:flutter_test`.
461+
Removing deprecated APIs from the framework are not currently planned. In the past, deprecations were removed after a set
462+
amount of time. This is not currently in practice. If and when we do resume removing deprecated APIs, it will be announced
463+
across several channels like the [flutter-announce group](https://groups.google.com/g/flutter-announce), and the
464+
[Discord](../contributing/Chat.md).
464465

465466
## Skipped Tests
466467

0 commit comments

Comments
 (0)