Release v1.13.0

[arminru]

This PR prepares the changelog for this month's spec release and adds some missing entries.

[bogdandrutu]

Please resolve #2726 before, to not release the new direction changes without a clear guidance.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[tigrannajaryan]

Please resolve #2726 before, to not release the new direction changes without a clear guidance.

@bogdandrutu do you want full resolution of #2726 or it is enough to if we merge #2748 which reverts #2617 and we can work on resolving #2726 fully after the release (including adding better guidance about usage of attributes vs separate metrics)?

Change reverted by #2748

[reyang]

Please resolve #2726 before, to not release the new direction changes without a clear guidance.

@bogdandrutu this should have been resolved by #2748, PTAL.

[tigrannajaryan]

Note that #2762 is a release blocker.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[carlosalberto]

@open-telemetry/specs-approvers The last blocking item has been merged - I suggest we release later today. Please take a look, etc.

[tigrannajaryan]

I think we need to make sure #2789 is seen by as many maintainers as possible to avoid surprises (some languages already started implementing the Scope attribute in the wrong way and have to revert it). The PR was created only 2 days, so I am not sure people are aware of this change.

I posted in Slack to raise awareness. I suggest that we give at least 2 days before we make 1.13 release.

[carlosalberto]

@tigrannajaryan Makes sense - early Friday as release date (as long as no complains happen) sounds good enough?

[tigrannajaryan]

Sounds good. In the meantime please circulate #2789 everywhere with everyone you think may be impacted or have an opinion.