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

[user456]

On Tuesday, 4 July 2023 at 11:08:02 UTC, Mike Parker wrote:
> I'm able to report on a couple of decisions that we reached 
> [...]
> * 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

There's a TZ problem here. The first PRs were submited before 
your annoucement and lead to confusion:

e.g 
https://github.com/dlang/dmd/pull/15379#issuecomment-1619628624

or quote from IRC

> [08:56] * DFeed [GitHub] Walter‎Bright opened dmd pull request 
> #15380 ("revert deprecation of scope class"): 
> https://github.com/dlang/dmd/pull/15380
>[08:57] <Herringway> oh no what is walter doing now
>[09:02] <Herringway> did I waste my time keeping up with 
>deprecations...?
>[09:05] <-- opticron (~opticron at 136.53.58.220) a quitté ce 
>serveur (Server closed connection).
>[09:06] --> opticron (~opticron at 136.53.58.220) a rejoint ce 
>canal.
>[09:13] <opDispatch> yeah, earlier I was about to drop a comment 
>about the tooling but actually dparse still supports body 
>apparently

so... for a few hours people thought it was a Walter's fad and 
not a well defined direction.