Minor release for Azure Exporter

[lzchen]

The PR as of 07/03/19 merges the current master branch into v0.6.x.
The changelog/versions are changed from 0.x.xdev to the release versions.
Changelog/version in Azure are bumped to the release version (0.3.1)
Django will be done in a different PR.

[reyang]

It looks like we're missing some *.py files in this PR, with the current PR, the only thing released would be the change log and version.

[c24t]

You'll have to merge this into the release branch and update the required versions in setup files to get this packaged and released, see #670 and #631 for recent examples. @reyang may be able to help with packaging this.

[c24t]

Change this to the date the package is released on PyPI.

[c24t]

Micro version updates are usually small and backwards-compatible, this looks like at least a minor-level change to me. https://www.python.org/dev/peps/pep-0440/#semantic-versioning.

[c24t]

Why put these in the same PR?

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

[lzchen]

The PR as of now merges the current master branch into v0.6.x.
The changelog/versions are changed from 0.x.xdev to the release versions.
Changelog/version in Azure are bumped to the release version (0.3.1)
Django will be done in a different PR.

[reyang]

LGTM.

[lzchen]

@reyang Are you able to sign the CLA or does @c24t have to add the label?

[reyang]

@reyang Are you able to sign the CLA or does @c24t have to add the label?

I don't have access to unblock Google CLA. My suggestion is that instead of cherry picking commits, just taking the file changes.

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

[songy23]

The base branch has an unnecessary rule:

The base branch requires all commits to be signed.

It prevents one user cherry-picking a commit from another user. If we can disable it, this PR should be good to merge.

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[lzchen]

@songy23 Good to know. I removed the outstanding commit and applied them manually myself. Should be good to merge.