Identify all commits required to be cherry-picked for v2.066.0-b2. If there are no cherry picks identified on this ticket by 0700 UTC (0000 PDT), the issue will be close and v2.066.0-rc1 will be created and published.
Comment #1 by code — 2014-07-04T01:09:17Z
How do you want release blockers to be handled? https://issues.dlang.org/show_bug.cgi?id=12958 (core.checkedint being broken) either needs to be fixed, or we need to rip core.checkedint out again (it is a new addition). Publishing a known-bad module would not be a good idea.
Comment #2 by edwards.ac — 2014-07-04T01:49:47Z
If a fix cannot be identified 48 hours prior to going live, it should be removed.
Comment #3 by edwards.ac — 2014-07-05T11:56:38Z
(In reply to Andrew Edwards from comment #0)
> Identify all commits required to be cherry-picked for v2.066.0-b2. If there
> are no cherry picks identified on this ticket by 0700 UTC (0000 PDT), the
> issue will be close and v2.066.0-rc1 will be created and published.
Meant to say by 0700 UTC (0000 PDT) on 7 July.