Identify all commits required to be cherry-picked for v2.065.1-b1. If there are no cherry picks identified on this ticket by 0700 UTC (0000 PDT), the issue will be close and no future attempt will be made at a point release for the v2.065.
Comment #1 by edwards.ac — 2014-07-05T11:59:39Z
(In reply to Andrew Edwards from comment #0)
> Identify all commits required to be cherry-picked for v2.065.1-b1. If there
> are no cherry picks identified on this ticket by 0700 UTC (0000 PDT), the
> issue will be close and no future attempt will be made at a point release
> for the v2.065.
Meant to say by 0700 UTC (0000 PDT) on 7 July.
Comment #2 by mk — 2014-07-07T10:15:20Z
Why such early deadline ?
Comment #3 by edwards.ac — 2014-07-07T10:28:53Z
The review period is less than two weeks. Is important that we identify and get bugs fixed as soon as possible. Unless we are only going to review one beta and then produce release, it is important that we fix problems and get it out to be tested again. We simply cannot wait until the witching hour to do that.
Comment #4 by edwards.ac — 2014-07-08T03:23:11Z
After further consideration, the maintenance release for v2.065 will is postponed until version September 15. The v2.065.1-b1 will be prepared and released on 1 September. Please submit candidates for cherry picking by 30 August.