BREAKING CHANGES
thinkingserious opened this issue · 3 comments
As a result of your feedback and as a continuation of the execution of our long term roadmap, there will be breaking changes coming soon. The last time we had a major breaking change, it was for the implementation of v3 Web API support. We announced those changes here on GitHub along with some instructions on how to test and provide feedback.
The feedback we got was amazing, but we didn't quite get the amount or thoroughness of feedback we were hoping for.
We want to continue improving this iterative process, so we are reaching out to you for feedback in order to determine the optimum way to move forward as this library is designed to be community driven, SendGrid led.
Please take a moment to share your thoughts with us.
Following are some ideas we are considering, we will likely choose one from Execution and one from Communication, but not all of the items below.
Execution (for large changes):
- Utilize the pre-release functionality in GitHub to gather feedback and contributions to a specific branch
- Communicate through a dedicated GitHub issue that references that pre-release branch (e.g C# Dynamic Update)
Communication:
- Continue using GitHub issues
- Opt-in email newsletter for announcements
- Opt-in email mailing list
- Dedicated social media account (e.g. @sendgrid_libraries)
How do you prefer to get these announcements? Is this too much? Too little? Please let us know!!
As always, we are listening carefully and are looking forward to working with you.
Note: We will always follow the semver.org convention of using major point releases to signify breaking changes. Please DO NOT auto-update your dependencies. It is important to take a look at the CHANGELOG or releases to find out how the breaking changes will impact your code.
Could you not have at least created a separate branch for the V2 client so I can use that temporarily. For me, this breaking change came without warning.
@danhardman have you tried this? https://github.com/sendgrid/sendgrid-go/blob/master/TROUBLESHOOTING.md#v2
@thinkingserious Appreciate it!