DMD 1.006 release

[Henning Hasemann]

> This seems a sensible change. Version.Major.Minor is very common and 
> very intuitive. Version for code incompatible changes, Major for new 
> additions to the spec, minor for bug fixes. You can keep your current 
> numbering scheme for minor ticks. Thus 1.0.001, 1.0.002, etc. As Miles 
> suggests, you could even retroactively bump the new "major" version to 
> reflect the new features (mixins and compile time functions).

votes++