Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Future Plan #131

Open
ripytide opened this issue Aug 8, 2024 · 3 comments
Open

Future Plan #131

ripytide opened this issue Aug 8, 2024 · 3 comments

Comments

@ripytide
Copy link
Contributor

ripytide commented Aug 8, 2024

I thought it was worth discussing the specifics of when to deprecate legacy items, several options I can think of:

  • Deprecate everything legacy immediately
  • Deprecate everything legacy in stages (how long between stages? what goes in each stage?)

There is also the question of when/how to remove the legacy items after they have been deprecated and a reasonable amount of time has passed, and what that reasonable amount of time should be.

It might also be worth documenting the decisions to these questions in the readme, so as the information is readily available to users, and then we just need to follow the plan.

@kornelski
Copy link
Owner

I'd like to give users some time to catch up with the existing updates and deprecations.

@kornelski
Copy link
Owner

I don't know how crates are going to migrate Gray now. Without the legacy flag it's not possible to swap v08 to v09, and without the Deref trick, the same source code can't be compatible with both.

@ripytide
Copy link
Contributor Author

I don't see an alternative to a hard-migration for the Gray pixel type, apart from people just deciding to not migrate, which is their prerogative.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants