jgraham
commented
3 years ago I want to switch Gecko over asap after upstream, but not before. I also don't want Gecko on 2.7 next year. So from my point of view doing the GitHub change on the last week of November and then doing the Gecko change the first week of December seems fine, although there could be breakage that doesn't happen upstream (I think I checked most things but not everything). So from my point of view this timetable is tight but doable. If we were going to slip dates I'd like it to be extending the vendor "deadline" to mid Jan or 1st Feb. and moving the end of Py 2 support to match. Obviously the longer the overall transition period is the more chance we get get cross-version breakage. So if others have concerns we can make that kind of change, but I think this timetable can work for gecko.
stephenmcgruer
I'm wondering if the timeline isn't too tight. I'd assume we lost at least the last two weeks of the year to various people's holidays, so that leaves about 5 weeks at best from today to get everything finished on our side and on the vendors's side. Moving the timeline by two weeks or a month might mean people don't have to rush as much. I don't know how urgently people need to move this along, though, so happy to be overruled on this if it seems feasible to the people who are going to do the work.