DMD release candidates

[Frank Benoit]

I would like to see release candidates for DMD releases.

Each new DMD release can have regression bugs. Each new release may fix 
one bug, but other new features (D2.x) or just other bug fixes may 
introduce other regressions.
User with a big code base have therefor a good chance to get a serie of 
releases which are not usable for their software.

So i suggest release candidates.
Release a DMD version as eg. 1.031RC1, then wait some days. If 
regression bugs show up, fix only them and create with that 1.031RC2. 
Only do that with regressions. If then no more regressions show up, 
create the 1.031 release as a copy of the latest release candidate.

This would give developer the best chance to have newest DMD really 
available for their software. And this again makes it possible that 
those users can create bug reports with the newest DMD release.