LGTM. Release notes to review?

Excluded from release notes:
#1745
#1759
#1780
#1798

Draft Release Notes

Core

• Tolerate server-generated timestamps w/ truncated nanoseconds. (Timestamp nanos parsing broken for '2016-05-09T18:49:00.655319Z' #1783, Tolerate timestamps w/ truncated nanos. #1785)

Search API

• Drop support for the API, as it has never moved from whitelist-only / alpha status, and its future is questionable. (Adding note about Search API whitelist. #1741, Removing Search API. #1750)

Monitoring API

• Include gcloud.monitoring system tests in the set run by default on Travis. (Add logging and monitoring to the set of system tests run by default. #1746)
• Define __all__ in gcloud/monitoring/__init__.py. (Define __all__ in gcloud/monitoring/__init__.py. #1747)
• Allow convenient filtering of metric descriptors by type prefix. (Allow convenient filtering of metric descriptors by type prefix. #1751)
• Remove unsupported metric type, MONEY. (The API does not support ValueType.MONEY. #1752)
• Update URL for Monitoring API V3 documentation landing page. (Update URL for Monitoring API V3 documentation landing page. #1757)

Logging API

• Include gcloud.logging system tests in the set run by default on Travis. (Add logging and monitoring to the set of system tests run by default. #1746)

Pubsub API

• Ensure that example snippets are testable, and fix those which broke. (Make pubsub example snippets testable. #1690, Pubsub snippet fixups #1765)
• Skip IAM Policy system tests when running under the emulator (which lacks IAM support). (Skipping IAM system tests when running in emulator. #1748)
• Skip IAM Policy system tests whn the current user holds insufficient privileges. (Avoid get / set of IAM policy if current account doesn't have permission #1782)
• Enumerate all IAM roles / permissions used by the Pubsub API. (Enumerate all roles / permissions for Pubsub IAM. #1776)
• WIP toward supporting Pubsub-over-gRPC using GAX. (Add 'gax-google-pubsub-v1' dependency to 'grpc' extra. #1753, Implement a GAX version of '_PublisherAPI'. #1764, Making the tox install of the gRPC extra quiet. #1794, Add GAX-based _SubscriberAPI. #1795)

DNS API

• Fix name of method used to initiate a changeset in usage docs. (DNS usage: fix name of method used to initiate a changeset #1769)

Bigtable API / Happybase

• Remove mention of undocumented HappyBase functions. (Removing mention of undocumented HappyBase functions. #1773)
• Allow use of Client as a context manager. (Add context manager for Bigtable client. #1797)

BigQuery API

• Ensure that mulitpart bodies are always bytes. (BigQuery upload_from_file unicode file-like must be opened in binary-mode if it's more than RESUMABLE_UPLOAD_THRESHOLD, otherwise str-mode. #1760, Ensure that mulitpart bodies are always bytes. #1779)

Datastore API

• Allow heterogeneous meanings for datastore list properties. (Allowing heterogeneous meanings for datastore list properties. #1758)

Release notes LG but I don't think "Add Travis Build ID to resource names created by system tests" is necessary

@tseaver Just noticed #1758 was left out. That's actually a "bug" fix worth noting.

Ditto on #1751, #1752, #1776, #1779, #1785 being user facing

@dhermes I was in the midst of editing them.

I don't know how you normally handle the post-merge release process. I would probably create a tag, push it to this repo, and then copy the release notes onto the "Releases" tab entry.

Post merge I create a tag via:

$ git tag 0.14.0
$ git push official 0.14.0  # I believe you call the remote "upstream"

and then visit https://github.com/GoogleCloudPlatform/gcloud-python/releases/edit/0.14.0 and manually paste the release notes

I rebased to pick up #1797, and will merge, tag and edit the release once Travis passes.