Wheels tweak and docs

[dhermes]

No description provided.

[dhermes]

Can see rendered update at:
https://github.com/GoogleCloudPlatform/gcloud-python/blob/5d9b46acbab54b032b55825ee992819b06e2246b/CONTRIBUTING.rst

[coveralls]

Coverage remained the same when pulling 5d9b46a on dhermes:wheels-tweak-and-docs into ce7f890 on GoogleCloudPlatform:master.

[tseaver]

LGTM

[dhermes]

Thanks @tseaver.

I was a little hesitant to write

The current value is::

    EXTRA_TOX_ENVS="coveralls regression"

since "current" doesn't really have a meaning as we refine our tests, we may update it and need ourselves (or CONTRIBUTErs) to update this document while also travis env set EXTRA_TOX_ENVS with a new value in the gcloud-python-wheels project.

WDYT?

[tseaver]

You could probably just ditch that part.

[dhermes]

Well future maintainers need to know if they introduce tox environs that live outside of envlist, the corresponding dependencies won't be built by gcloud-python-wheels unless an action is taken.

(We could address this by making gcloud-python-wheels even more complex and parsing all tox uses in .travis.yml but this requires explicitly putting tox rules in the Travis config, like we do with coveralls and regression scripts wrapping multiple scripts.)

[tseaver]

I meant the part which you highlighted (showing the current value).

[dhermes]

@tseaver Gotcha. Updated and made sure the value is unencrypted in the project so people can see it before updating.

[coveralls]

Coverage remained the same when pulling 544c22c on dhermes:wheels-tweak-and-docs into ce7f890 on GoogleCloudPlatform:master.

[tseaver]

I'm confused: what does the 'EXTRA_TOX_ENVS' bit have to do with anything encrypted?

[dhermes]

I was just referring to them the way they are referred to in the Travis docs:

By default, the value of these new environment variables will be hidden from the export line
in the logs. This corresponds to the behavior of encrypted variables in your .travis.yml.

[tseaver]

+1 for merge.