Planning Update June 23 & 30 -- Bugzilla to GitHub; Deprecations

[ryuukk_]

On Tuesday, 4 July 2023 at 11:08:02 UTC, Mike Parker wrote:

> ### Deprecation policy

> * nothing should be deprecated unless there's a very compelling 
> reason ("this feature was a mistake and people shouldn't be 
> using it" is not a compelling reason)
> * every deprecation should have a clear path for migration, 
> automated if possible
> * the person implementing a deprecation will be responsible for 
> updating projects that trigger it in our BuildKite tests
>

100% agree, deprecation and breaking changes are needed to 
cleanup past mistakes, but proper migration path should ALWAYS be 
included to avoid that kind of issues

Also, for the love of god

https://github.com/dlang/dub/issues/2617 - "Get rid of deprecate 
warnings"
https://github.com/dlang-community/DCD/issues/722 - "Get rid of 
deprecate warnings"

I got ignored months ago for asking to clean up and fix ton of 
deprecation warnings

This should NEVER happen on projects that are hosted on official 
repos

If the head is careless, how do you expect everyone else to care?