On Wed, Jul 25, 2018 at 10:22 AM, Juergen Gross <jgross@xxxxxxxx> wrote:
fFFFFFFR.......ffFFFFFFR.......ffFFFFFFR.......f
We can rule out several variants with release dates just before or in a
holiday season:
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Xx.XXXXX...xxxx...........xxXXXXx..............X holidays
ffFFFFFFR.......ffFFFFFFR.......ffFFFFFFR.......
.ffFFFFFFR.......ffFFFFFFR.......ffFFFFFFR......
Best fit seems to be releasing in first half of March/July/November. The
main clash seems to be Chinese new year in the freeze period, but
avoiding that would mean we'd have to either move into Christmas or
Eastern, or to use a schedule with varying periods.
Please remember that Chinese new year is only 2 weeks long (at varying
dates) so only 2 weeks of the freeze period are hit. Next year the
Chinese new year will be at February 5th.
For my 4.12 plan I've added some extra weeks between last posting date
and release date to accommodate for the holiday seasons, resulting in
my suggestion.
Thanks for the detailed analysis Juregen. This seems good to me.-George
This looks good to me also. To address Julien's concerns, we could also consider an earlier Last posting date/Hard code freeze date for Arm related code to work around Julien's holiday plans. I think this would be entirely OK and set expectations of contributors accordingly. But maybe this is not necessary if Julien and Stefano can agree a work split somehow.
Alternatively we could communicate absences of key reviewers say in November to set expectations of contributors for the final stretch of the release cycle. In other words, if a key reviewer is away, then contributors will need to get series into good shape before their reviewers go on vacation.
Regards Lars
|
