Prepare release 1.1.0 (open-telemetry#523)

* Prepare release 1.1.0

Signed-off-by: Bogdan Drutu <[email protected]>

* Update CHANGELOG.md

Co-authored-by: Piotr Kiełkowicz <[email protected]>

* Update CHANGELOG.md

* Update CHANGELOG.md

Co-authored-by: Yuri Shkuro <[email protected]>

---------

Signed-off-by: Bogdan Drutu <[email protected]>
Co-authored-by: Piotr Kiełkowicz <[email protected]>
Co-authored-by: Yuri Shkuro <[email protected]>

Add maturity JSON entry per package

This is because otherwise, when merged a new package will be automatically stable as JSON.

Clarify uniqueness of Scope attribute keys

We use exact same wording as we already have for LogRecord, Span, etc.

Prepare for v0.19.0 release (open-telemetry#420)

Signed-off-by: Bogdan Drutu <[email protected]>

Prepare 0.18.0 release (open-telemetry#391)

* Prepare 0.18.0 release

* Update CHANGELOG.md

Co-authored-by: Joshua MacDonald <[email protected]>

Prepare 0.17.0 release (open-telemetry#389)

Prepare 0.16.0 release (open-telemetry#377)

Prepare for release v0.15.0, update release v0.14.0 changelog (open-t…

…elemetry#367)

* Release v0.14.0

* Create CHANGELOG.md (open-telemetry#368)

* Update CHANGELOG.md (open-telemetry#369)

* Update CHANGELOG.md (open-telemetry#370)

* Update CHANGELOG.md (open-telemetry#371)

Deprecate LogRecord.Name field (open-telemetry#357)

The field is removed from the spec: open-telemetry/opentelemetry-specification#2271

I am deprecating it for now, to give some time to existing users to get rid
of it (most notably in the Collector).

This will be removed March 15, 2022 (after the Collector cleanup).

Prepare to release 0.13.0 (open-telemetry#361)