Gsutil

=======================================
New features
------------------
- When using the JSON API, the "ls -L" and "stat" commands now print an object's
storage class update time if it differs from the object's creation time; this
occurs when the storage class has been changed due to the bucket's lifecycle
management configuration.
- Listing a bucket's metadata via "ls -Lb" now prints its metageneration.

Bug Fixes
------------------
- When specifying custom metadata values using the top-level -h option, such
values may now include unicode characters as well as multiple ":" characters.
- For Cloud SDK (gcloud) distributions of gsutil, if you have configured the
Cloud SDK to not pass credentials to gsutil (by running "gcloud config set
pass_credentials_to_gsutil false"), gsutil will now correctly work with
credentials obtained via "gsutil config". This would previously result in an
error with a message to run "gcloud auth login". Additionally, the "gsutil
config" command no longer prompts users to run "gcloud auth login" if this
option is set to false. This should allow switching between stand-alone
gsutil installations and gcloud-packaged gsutil installations more easily.
- The config_file_list section in debug output now displays files in the order
that they are loaded.

Other Changes
------------------
- Added XML support for some commands which previously only worked via the JSON
API ("lifecycle" and "defstorageclass").
- Several documentation updates and clarifications.

=======================================
New features
------------------
- The cp command now supports reading from and writing to named pipes.

Bug Fixes
------------------
- Fixed issue where tab completion wasn't working.
- Fixed issue when using the XML API where gsutil would fail to parse bucket
metadata for buckets using Lifecycle rules containing the SetStorageClass
action or MatchesStorageClass condition.

Other Changes
------------------
- Removed -o flag from "notification create" command. The same functionality is
available with the -p flag; the -o flag had been mistakenly added in a
previous change.
- Removed the alpha disclaimer from the iam command help text.
- Several documentation updates and clarifications.

=======================================
New features
------------------
- Added bucket label support to gsutil. For more details, see
https://cloud.google.com/compute/docs/label-or-tag-resources.
- Added the label command, which can be used to get, set, and change the labels
for an existing bucket (known as "tags" for S3 buckets).
- Listing a bucket via "gsutil ls -Lb" now also displays the labels, if any
exist, that are currently set on it.

=======================================
New Features
------------------
- Added support for configuring GCS Cloud Pub/Sub notifications. For more
details, see https://cloud.google.com/storage/docs/pubsub-notifications.
- Added support for specifying canned ACLs when using the rsync command.

Bug Fixes
------------------
- Fixed a bug where error messages about invalid object names did not correctly
display the problematic object name.

=======================================
Bug Fixes
------------------
- Fixed "referenced before assignment" error in some copy_helper exceptions for
resumable uploads and non-resumable cloud-to-local downloads.
- The setmeta command now properly supports case sensitivity in custom metadata
keys when using the JSON API.
- Fixed a resource leak affecting Windows in cases where single-process,
multithreaded parallelism is used that would result in an OSError with the
message "Too many open files".
- Fixed HTTPError initialization failure in signurl command.
- Fixed signurl issue where attempting to validate short-lived URLs on a slow
connection would fail because of URL expiration.
- Fixed a bug where cp -r would not properly resolve wildcards for
cloud-to-cloud copies.
- Fixed a bug where cp -e -r would copy symlinks.
- Fixed a bug where cp -P would fail on Windows.
- Fixed a bug where version -l might not show all boto configuration files.
- Running perfdiag now only lists the objects that were created by that run of
perfdiag. This fixes an issue where running perfdiag against an existing
bucket with many objects in it could take a long time.


Other Changes
------------------
- Simplified parallelism when using a single process with multiple threads.
With this change, gsutil will spawn a new thread pool per level of
parallelism. As an example, if you specify that you want a
parellel_thread_count of 24, this will result in 24 worker threads, except
when you're using parallel composite uploads or sliced downloads, in which
case 48 (24 * 2) worker threads will be used.
- Extended the early deletion warning threshold when moving Coldline objects
to 90 days after object creation.
- Improved several error messages and warnings.
- Several documentation updates and clarifications.

=======================================
New features
------------------
- Added per-object storage class functionality to gsutil. For more details, see
https://cloud.google.com/storage/docs/per-object-storage-class.
- Added the defstorageclass command, which can be used to get and set an
existing bucket's default storage class.
- The cp, mv, and rewrite commands now support the "-s" option, allowing users
to specify the storage class for destination object(s). When no storage class
is specified, the object's storage class will be assigned from either its
bucket's default storage class (cp/mv commands) or the source object's
storage class (rewrite command).

Bug Fixes
------------------
- Fixed a bug in POSIX preservation for the cp and mv commands where POSIX
attributes were not propagated to cloud objects, even when the -P flag was
present.
- Fixed a bug in setmeta where removing custom metadata would add an
empty-string value if the key did not already exist.
- Content-Type is now obtained from symlink targets, rather than symlinks
themselves, when the use_magicfile option is set in the .boto configuration
file.

Other Changes
------------------
- Analytics reporting now includes performance metrics such as average
throughput and thread idle time.
- The iam set command now supports a -e option to specify an etag precondition
check. The IAM policy file returned by iam get and used by iam set has also
been altered to include this field.
- Default limit for max number of processes changed to 64.
- Several documentation updates and clarifications.