On December 16, 2019 5:39:06 PM GMT+01:00, Jeff Law <l...@redhat.com> wrote: >On Mon, 2019-12-16 at 13:53 +0000, Joseph Myers wrote: >> >> > > However, we should also note that stage 3 is intended to last two >months, >> > > ending with the move to git >> > > <https://gcc.gnu.org/ml/gcc/2019-10/msg00143.html> >> > > <https://gcc.gnu.org/ml/gcc/2019-11/msg00117.html>;, and given >that it >> > > didn't start at the start of November as anticipated in the >originally >> > > proposed timetable, that implies corresponding updates to all the >dates. >> > > By now, enough people are away until the new year that now isn't >a good >> > > time for deciding things anyway. >> > >> > The idea was to do it while most people were away to have the least >> > impact. The timeline https://gcc.gnu.org/wiki/GitConversion does >say we >> > can slip for logistical reasons the read-only date (2019/12/31) by >a >> > few days. >> >> It was also that doing it at the end of stage 3 would mean the least >> disruption to development for stage 3. That suggests converting over >the >> weekend of 18/19 January, given the current stage 3 timings. >My recollection was the timing was meant to land roughly at the stage3- >>stage4 transition. So the question is whether or not we're on target >with that. Based on the regression counts, probably not at this point, >but I'll let the release managers chime in on that point. >
Fortunately that's a pure timing thing and I'd expect stage3 to end mid January, possibly scrapping off a week to help the git conversion. Richard. >Jeff
