In this, there's mention of changing Landmark to FacialFeature. I think that might be good to do before beta. WDYT?

I looked and I didn't see anything about "alpha" in the docs so I think those are set.

@dhermes I just remembered I forgot to bring this up at the standup.

On the GAPIC side, we bump versions to 0.90 when they hit beta. However:

(1) We did not do that for other libraries here, and
(2) That would be inconsistent with how we track everything to core 0.23.x

The beta designation here entails an expectation change, but not so much an actually significant code change. I am willing to bump to 0.24.0 in principle but it would entail bumping everything (which is kind of time consuming). Also fine with just bumping to 0.23.3, and what we changed is "hey, beta status".

Thoughts?

As a note, when we go GA, we will need to bump the version of the GA libraries to 1.x

@lukesneeringer That expectation works for me. Also, keep in mind we can do an umbrella release without "bumping everything": simple change the API at hand and rev the version (we don't need 23<-->23 to match)

Concur, although I think the consistency is valuable in the immediate term. I am also hoping google-cloud-core is much more stable now than it was a couple months ago.

So, am I good to merge this?

Sure thing

Merged. @daspecster Please cut a release and remember to manually bump docs so we see the beta designation on the index page.

@lukesneeringer nothing was changed in the "docs", just the README here just FYI.

Release tag made.
https://github.com/GoogleCloudPlatform/google-cloud-python/releases/tag/vision-0.23.3