Release process and backwards compatibility

[Dicebot]

On Saturday, 9 March 2013 at 05:11:40 UTC, Jesse Phillips wrote:
> On Saturday, 9 March 2013 at 04:55:06 UTC, deadalnix wrote:
>> This isn't the type of change you can release without any 
>> damage mitigation plan.
>
> Don't leave us hanging. What is your damage mitigation plan?
>
> My desire is made elsewhere, but I don't think there is 
> anything to do, code will break, instead dmd 2.062.1 should get 
> released and contain regression and non-breaking bug fixes.

As deadalnix have said (and I fully agree here), "The problem 
isn't really breaking the code. It is more about how it is 
done.". Thus, proper announcements and release model change 
actually is damage mitigation plan. Not really an excellent one, 
but better than having none currently.