dmd development model.

[Moritz Warning]

On Mon, 12 Oct 2009 13:50:14 -0700, Walter Bright wrote:

> Eldar Insafutdinov wrote:
>> If dmd delepers contributed every change to the VCS separately, it
>> would be much easier to track down the change that caused the issue.
> 
> Yeah, that's probably a good idea.
> 
>> From my side I could test the version of dmd from trunk every 2 days
>> and file bugs as they appear. That's how most of the open source
>> projects work, and this model works fine. Few days before the release
>> there can be an appropriate notice, so that people could test their
>> code. That would make dmd releases less buggy. I know that Walter sends
>> the compiler to tango devs prior to release, but that's not a robust
>> solution to the problem, developers may not have time at the moment for
>> example.
> 
> I do send it out for beta, but nobody responds.

Thanks for your reply.

I think the people in question are too busy with life atm.
but I've also heard that there might not be enough time for review.

Anyway, more frequent commits would
make this procedure unnecessary at all. ;)