IssueTracker

Slipped Oct iteration. We... don't really have a plan here yet, but this is P1 to stop the bleeding.

libraries where all resources are currently considered public but have never been tracked

Safest route for external developers is to make all existing resources officially public. That's going to be more work since we can't just copy the public.txt file. It also means that internal developers are locked into their existing resources, which is... safer, but not good for evolution of libraries.

Easiest route for internal developers (and our team) is to make all existing resources officially private. That will potentially break g3 drops and third-party libraries; however, it's an easy workaround given that we don't do resource namespacing yet. Developers can just define the resource that they (or their dependency) needs. Anyone using a dependency's R class directly is already hosed, anyway, so we'll ignore that.

Going to move forward with "fixing" the libraries which accidentally exposed all their resources as public.

Tentatively, we'll:

1. Require a public.txt to exist in the AAR, with a failure message along the lines of "At least one public resource must be defined. If your library has no public resources then please define a single, empty <public /> element in res/values/public.xml."
2. Add a public.xml file as described to all failing libraries
3. Be very, very explicit about the change in release notes
4. Deal with the fallout in g3

Estimate is 2 due to g3 issues.