chore: prep release 1.5.0

[pankajagrawal16]

Issue #, if available:

Description of changes:

Checklist

• Meet tenets criteria
• Update tests
• Update docs
• PR title follows conventional commit semantics

Breaking change checklist

RFC issue #:

• Migration process documented
• Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[msailes]

👍

[heitorlessa]

Isn't that a major update?

What's the cost in keeping both but leaving only one documented?

[pankajagrawal16]

That's how we deprecated it initially by removing its reference from our docs. So docs don't have these attributes referenced. It won't lead to any surprises functionally, since this will lead to a compile time error for users.

Cost of keeping deprecated attribute forever is basically technical debt.

[heitorlessa]

Forever is a long time. you can cut a major release :) If all of you are fine with the decision (I wouldn’t), then please make sure this is called out in the release notes too

…

On Tue, 30 Mar 2021 at 12:57, Pankaj Agrawal ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In CHANGELOG.md <#345 (comment)> : > @@ -8,8 +8,22 @@ This project follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) fo ## [Unreleased] +## [1.5.0] - 2021-03-30 + +* **Tracing**: Removed deprecated attributes on `Tracing` annotation. If you are still using `captureResponse` and `captureError` That's how we deprecated it initially by removing its reference from our docs. So docs don't have these attributes referenced. It won't lead to any surprises functionally, since this will lead to a compile time error for users. Cost of keeping deprecated attribute forever is basically technical debt. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#345 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZPQBDKBBQDV3DWBQ7N7M3TGGVCBANCNFSM42BYLYRA> .

[pankajagrawal16]

Forever is a long time. you can cut a major release :) If all of you are fine with the decision (I wouldn’t), then please make sure this is called out in the release notes too
…
On Tue, 30 Mar 2021 at 12:57, Pankaj Agrawal @.> wrote: @.* commented on this pull request. ------------------------------ In CHANGELOG.md <#345 (comment)> : > @@ -8,8 +8,22 @@ This project follows Keep a Changelog fo ## [Unreleased] +## [1.5.0] - 2021-03-30 + +* Tracing: Removed deprecated attributes on Tracing annotation. If you are still using captureResponse and captureError That's how we deprecated it initially by removing its reference from our docs. So docs don't have these attributes referenced. It won't lead to any surprises functionally, since this will lead to a compile time error for users. Cost of keeping deprecated attribute forever is basically technical debt. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#345 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZPQBDKBBQDV3DWBQ7N7M3TGGVCBANCNFSM42BYLYRA .

Its no problem to cut a major release as well. Or maybe we can wait with the removal change until we really need to make a major release. Thoughts @msailes ?

[heitorlessa]

If that helps, for Python at least, we’re gonna start publishing our list of tech debts we want to cut in 2.0. I’ll ping once it’s public hopefully next week On Tue, 30 Mar 2021 at 13:08, Pankaj Agrawal ***@***.***> wrote:

…

Forever is a long time. you can cut a major release :) If all of you are fine with the decision (I wouldn’t), then please make sure this is called out in the release notes too … <#m_2236942094368262142_> On Tue, 30 Mar 2021 at 12:57, Pankaj Agrawal *@*.*> wrote: @.** commented on this pull request. ------------------------------ In CHANGELOG.md <#345 (comment) <#345 (comment)>> : > @@ -8,8 +8,22 @@ This project follows Keep a Changelog <https://keepachangelog.com/en/1.0.0/> fo ## [Unreleased] +## [1.5.0] - 2021-03-30 + +* *Tracing*: Removed deprecated attributes on Tracing annotation. If you are still using captureResponse and captureError That's how we deprecated it initially by removing its reference from our docs. So docs don't have these attributes referenced. It won't lead to any surprises functionally, since this will lead to a compile time error for users. Cost of keeping deprecated attribute forever is basically technical debt. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#345 (comment) <#345 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZPQBDKBBQDV3DWBQ7N7M3TGGVCBANCNFSM42BYLYRA . Its no problem to cut a major release as well. Or maybe we can wait with the removal change until we really need to make a major release. Thoughts @msailes <https://github.com/msailes> ? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#345 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZPQBAHSVIXRSULZ3ISNJ3TGGWL5ANCNFSM42BYLYRA> .

[pankajagrawal16]

If that helps, for Python at least, we’re gonna start publishing our list of tech debts we want to cut in 2.0. I’ll ping once it’s public hopefully next week.

I am thinking maybe that's best way to solve it. Which means we can target more deprecated features as part of a single major release rather than bumping major release each time we remove a deperecated feature.

[pankajagrawal16]

@heitorlessa / @msailes Looks better?

[heitorlessa]

Thanks a lot for taking breaking changes into account. I'm sure customers will appreciate that.