(DRAFT) 0.18.0 Release Notes

Note This is the last release which supports Python 2.6.

Core/testing/hygeine

• Generate JSON documentation for consumption by gcloud-common application. (WIP: Json documentation generation #1775)

Storage

• Add support for streaming upload via file-like objects. (Support blob streaming for file-like objects #1914)
• Improve error message when platform does not support generating a signed blob URL. (Change error for generating signed URL #1966)

Pubsub

• Add support for auto-acknowledging pulled messages. (#798: Add support for auto-acknowledging pulled messages. #1636)
• Fix use of Batch for pull requests returning empty result sets. (Fix pubsub context manager exit error #1956)

BigQuery

• Make dataset, table, and synchronous query doc snippets testable (Make dataset snippets testable #1832, Make table snippets testable #1833, Make synchronous query snippets testable #1836)
• Fix Table.upload_from_file docs example. (Add quotes to CSV reference #1971)
• Add support for use_legacy_sql query property. (Adding BigQuery support for legacy SQL. #1992)
• Add support for udf_resources query property. (refork and fix of #2015 (UDF Support) #2029)

Bigtable

• Fix V2 docstrings (Fixed spelling and formatting. #1945, Bigtable V2 docs fixes lost in merge #1948).
• Make HappyBase Table.enable_table, Table.disable_table, Table.is_table_enabled, and Table.compact_table no-ops, rather than raising NotImplementedError. (Making HappyBase enabled/disabled checks into no-ops. #1997)
• Make HappyBase Table.counter_set conform to HBase semantics. (Make counter_set in HappyBase agree with HBase impl. semantics #2000)\
• Make HappyBase Table.create_table atomic. (Making HappyBase create_table() atomic. #2002)

Logging

• Fix system tests when GAX / gRPC is enabled (Fix GAX logging system tests #1952).
• Update branding from "Cloud Logging" to "Stackdriver Logging." (Update references from Cloud Logging to Stackdriver Logging #1962)

DNS

• Fix Zone.resource_record_set usage example. (Update DNS resource_record_set() #1977)

Error Reporting

• Initial client implementation (Add Error Reporting Client #1946).

@daspecster, @dhermes: Redone without the Github-UI-induced weirdness (and squashed). PTAL

LGTM.

nit: In the release notes, why have an empty line between every bullet?

@dhermes because markdown suckspenalizes the rendered form for improved readability in the source.

Does not compute. What do you mean? What is the readability penalty?

Its twofold: it treats all newlines as paragraphs, which makes editing paragraphs harder. And in the source form, bullet lists are easier to read with a line between each item, particularly where items might be longer than a single line.

And in the source form, bullet lists are easier to read with a line between each item

That's subjective. No worries though, I don't have any strong preference.

I deleted the lines anyway, as I agree the rendered form was inferior.