Fixed
Status Update
No update yet.
Comments
al...@google.com
Next steps:
- Discuss with API Council Leads the week of 4/10
al...@google.com
Bugjuggler: wait until 2023-04-10
bu...@google.com
Hi. I've received your bug and will wait until 2023-04-10 00:00 -0400 EDT and then assign the bug to alanv@google.com.
bu...@google.com
al...@google.com
Stepping back a bit, right now we have:
| File name | Reviewed | Checked |
|---|---|---|
current.txt |
x | x |
public_plus_experimental_current.txt |
x | |
restricted_current.txt |
* |
- Only for non-atomic groups
What we really want is the AND of:
| Annotation | Reviewed | Checked |
|---|---|---|
| (default) | yes | yes |
@RequiresOptIn |
yes | no |
@RestrictTo(LIBRARY) |
no | no |
@RestrictTo(LIBRARY_GROUP) |
no | * |
@RestrictTo(LIBRARY_GROUP_PREFIX) |
no | yes |
- No for atomic groups, yes otherwise
So I'm wondering if we can eliminate public_plus_experimental_current.txt and embed the "Checked" state into a Metalava flag. Then we'd have current.txt as reviewed APIs and restricted_current.txt as unreviewed (but still checked) APIs.
al...@google.com
Checked with Aurimas offline, it sounds like merging the two files and conditionally checking compatibility based on annotations would be feasible. This isn't urgent, so I'm re-scoping to cover that as well.
bu...@google.com
Hi. I've received your bug, you didn't specify what to wait for so I will wait for
Bugjuggler:
Bugjuggler:
Description
Health Connect, at least, would like experimental APIs reviewed up-front rather than after they have been promoted to non-experimental during the following alpha.