I just thought it would be useful to announce breaking changes, new
warnings and deprecations
added to the D language (dmd, druntime, phobos) in a separate mailing list.
It can be also used to discourage from using certain constructs.
Some examples:
---
dmd >= 2.056
New Warning for dangling else.
Detailed explanation....
---
phobos >= 2.055
Deprecated std.path.basename. Replacement std.path.baseName.
Detailed explanation...
---
The actual message format should be machine parseable.
martin

I just thought it would be useful to announce breaking changes, new
warnings and deprecations
added to the D language (dmd, druntime, phobos) in a separate mailing list.
It can be also used to discourage from using certain constructs.
Some examples:
---
dmd >= 2.056
New Warning for dangling else.
Detailed explanation....
---
phobos >= 2.055
Deprecated std.path.basename. Replacement std.path.baseName.
Detailed explanation...
---
The actual message format should be machine parseable.
martin

I don't know if we need a separate mailing list, but this information should
be part of the change log and posted on the announcements mailing list.
For example, the deprecation listed above was described in the change log as:
• std.path has been rewritten from scratch and has a completely new API.
Seems like more is needed. Maybe a wiki page or something with a list of
deprecations scheduled along with build numbers and dates?
Paul

They are, but they're mixed with other changes and bug fixes. You have
to read each item in the changelog to find the breaking changes. Listing
them separately would help greatly when updating code.

And they are not focused on what needs to be changed in your code.
But on a second thought it would be difficult to synchronize mails with
pull requests. Richer changelog entries could be of a help, submitted with
the pull requests.