google-cloud-python
google-cloud-python copied to clipboard
determine publishing policy for APIs with "experimental" parts, possibly via a mechanism to pin their libraries as "preview"
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.
We seem to be converging towards doing this. So to be explicit, the first library we would pin (mechanism TBD) to remain "preview" is
-
packages/google-maps-places/