Start of dmd 2.064 beta program

[Kagamin]

On Saturday, 19 October 2013 at 11:39:08 UTC, Iain Buclaw wrote:
>> > It has been about 3 months since the last release of the D
>> > front-end implementation.  Three years experience and 
>> > carrying
>> > out over 100 merges into GDC tells me that each time the
>> > development cycle starts edging towards it's fourth month, it
>> > makes things an absolute nightmare, in both the time consumed
>> > merging in the changes, and with time spent tracking down bug
>> > reports for unittests/testsuite cases that test backend code
>> > generation - with 2.060, 2.061 and 2.063 being the worst 
>> > releases
>> > I have ever had to deal with - before 2.060 the release 
>> > schedule
>> > (if it even qualifies as a 'schedule') was anywhere between 
>> > 1-2
>> > months.
>
> And a big +1 to that as well.

Can't merges be done without release at your discretion in a 
separate branch or repo? If you keep track of it monthly, then 
you would have less to merge at the time of release.