determine publishing policy for APIs with "experimental" parts, possibly via a mechanism to pin their libraries as "preview" #12721
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: process
A process-related concern. May include testing, release, or the like.
Determine whether we can merge and release #12709 even though some of the proto messages are marked as Experimental.
One possibility is to publish this library in a "preview" state and leave it as such until the "Experimental" code becomes stable. If we go with this approach, we would need to figure out how to pin the library as "preview" so we don't accidentally promote it to GA.
The text was updated successfully, but these errors were encountered: