Ensure v3 deprecation messages are useful for migrating people #4052
Labels
A-docs
Area: documentation, including docs.rs, readme, examples, etc...
C-bug
Category: Updating dependencies
E-help-wanted
Call for participation: Help is requested to fix this issue.
E-medium
Call for participation: Experience needed to fix: Medium / intermediate
Milestone
Inspired by a reddit thread. in preparing to release v4, we need to audit the deprecation messages in v3 to ensure they are sufficient for migrating people up so we can use it as a guided migration guide and focus the actual migration guide on the more subtle issues that aren't as easily handled
The text was updated successfully, but these errors were encountered: