A fresh perspective on the experimental-APIs issue just came to me: this should 
not hold up the 1.11 release. We were falling into the old trap of thrashing 
about debating how to do it, assuming we needed some solution for 1.11, but we 
don't. One of the rules of time-based releases: something that need not block 
it should not block it.

We should just pull the experimental APIs from the public API space (moving 
them into the private API space) and get on with the release.

This seems clearly the Right Way so I'm going to get on with it right away. 
Speak up if you see a show-stopper problem with that.

-- 
- Julian

Reply via email to