commit b0f7805ba3a42389cf2f6258f7d625082ecccf5e
author Jiyong Park <jiyong@google.com> Fri Jun 04 11:50:41 2021 +0900
committer Jiyong Park <jiyong@google.com> Fri Jun 04 11:50:41 2021 +0900
tree 9c2783063375dae14ea918b411e053f0cbde517a
parent cbab704881f7409baed66ed26c4be57d31355190

Set owner property on auto-specific interfaces

These two auto-specific interfaces are currently frozen at the version
1. However, there are many modules that are using V2 of these modules,
presumably with the expectation that the development for the V2
interface will soon get started.

This is becoming a blocker to the Android API freeze process because
such a use of non-frozen interfaces is prohibited after the API freeze.

There are three ways to solve this:

1) freeze the interfaces again so that V2 becomes the latest stable
version. But this is bad because there is no V2-specific changes (i.e.
V1 == V2 in terms of the API spec). Furthermore, the build system
doesn't allow adding a new version when the version is identical to the
previous version.

2) Replace all the references to the V2 interfaces with V1. This is not
ideal because this is against the desire to keep using the latest
version. Furthermore, the number of modules that needs to be touched are
many.

3) Set the `owner` property to the interfaces so that they are exempted
from the Android platform's API freeze process. This makes sense because
these interfaces are specific to Android auto which is a "different"
platform having its own release schedule.

Bug: 188713899
Test: m
Change-Id: I841e6a37dd2659a53480e08dab955835a7d14dd3