<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 03/23/2014 08:34 PM, Andrew Edwards
wrote:<br>
</div>
<blockquote cite="mid:532F3755.9020308@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 3/23/14, 3:28 PM, Martin Nowak
wrote:<br>
</div>
<blockquote cite="mid:532F35F6.9020200@dawg.eu" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 03/23/2014 03:06 PM, Andrew
Edwards wrote:<br>
</div>
<blockquote cite="mid:532EEA4F.9020507@gmail.com" type="cite">I
am just getting healthy again. Just in time for the
preparation of 2.066 beta 1.</blockquote>
Can you fill in the planed release month for 2.066 here (
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true"
href="http://wiki.dlang.org/Agenda#v2.066_.28.3F.3F.3F_2014.29">http://wiki.dlang.org/Agenda#v2.066_.28.3F.3F.3F_2014.29</a>).<br>
IMHO we're not yet in shape for a beta.<br>
</blockquote>
Sure can. The plan was that the beta would be released 4 weeks
after the most recent release. With a full two month review (1 for
beta and 1 for release) that should put release around May 19.<br>
</blockquote>
I think we need to discuss these timeframes to use our restricted
development resources most efficiently.<br>
<br>
- Porting a fix to a branch that diverted 2 month earlier is a lot
of extra effort.<br>
<br>
- 4 weeks is too little time to work on bigger features and review
time also binds developers.<br>
<br>
- There is only a limited attention span for beta testing.<br>
<br>
Something like 2 month until the next beta + 1 month for
testing/fixing seems like a better fit to me currently.<br>
</body>
</html>