Thanks @tswast. I want to make sure we get @daspecster in the loop on this, but he is out-of-country right now. Change content looks good (LGTM), I suppose we should merge and create an issue assigned to @daspecster?

Yeah, I'm wondering if we should wait to update this link. I'm not very happy with the state of the docs for 0.18.x. Besides not having links to previous versions #2073 , they are missing info #2072 and have broken links #2061

It's not really 0.18.x, it's the move to using the docs template in gcloud-common (but they do coincide)

@tswast @dhermes yeah I would like to get things cleaned up first if possible.

@tswast for future reference, the workflow we prefer has contributors (including us!) pushing changes to personal forks and then creating PRs from them. In your case, for instance, the push to a new branch triggered CI checks that normally occur only after merging the reviewed PR.

I've restarted the PR build to see if it can pass now that the missing GAX release issue is fixed.

@tseaver AFAICT all these extra checks come in when the PR is created via the GitHub UI.

@dhermes they come into play whenever a branch is pushed to this repository: it is possible for contributors to do that when editing through the UI, but they also have an option to put the changes in their own fork. I don't recall what the default for that choice is.

GitHub doesn't even give me the option to write the commit from the UI to my fork.

I guess the workflow has to be to fork, then edit in my fork and send PR from there, but that adds a lot of friction. :-(

Ah, I see now. Silly GitHub

@tswast but if you fork the repo you get a tshirt and stickers and stuff! jk...

So we merged a bunch of fixes for the issues I mentioned earlier.
There's still #2039 and I need to get autogeneration of the tags working. I should have it by tomorrow morning.

Replaced by #2147, deleting the branch