summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndroid API Council <no-reply@android.com>2024-04-22 13:24:17 -0700
committerAndroid API Council <copybara-worker@google.com>2024-04-22 13:24:46 -0700
commit10d0ac15add45ec9c8b4e787bc0a2948e034c6eb (patch)
tree5c7dce8a7c777d2a9830700bb6f3920d3b354faa
parent7fa8cf31687b1658af92dd67ebeb97532e1165f0 (diff)
downloaddocs-10d0ac15add45ec9c8b4e787bc0a2948e034c6eb.tar.gz
Document the intake form for Android API removal requests
PiperOrigin-RevId: 627137372 Change-Id: I769048b4d653f359a1b2af85f9f1b6571e027e31
-rw-r--r--api-guidelines/evolution.md8
1 files changed, 2 insertions, 6 deletions
diff --git a/api-guidelines/evolution.md b/api-guidelines/evolution.md
index 414b173..8354d74 100644
--- a/api-guidelines/evolution.md
+++ b/api-guidelines/evolution.md
@@ -220,12 +220,8 @@ to extend a class, abstract methods may still be soft removed.
### Hard removal <a name="hard-removal"></a>
Hard removal is a binary-breaking change and should never occur in public APIs.
-For system APIs, hard removals **must** be preceded by soft removal for the
-duration of a major release. Remove the entire implementation when hard-removing
-APIs.
-
-Tests for hard-removed APIs **must** be removed since they will no longer
-compile otherwise.
+If you have a strong justification for a removal, you can request for approval
+by submitting the 1 pager at go/request-android-api-removal.
### Discouraging {.numbered}