On 3/11/16 05:39, Sean McArthur wrote:
> What's great about the train schedule is that it's consistent. You know
> that if you can't quite wrap something up before the train departs, well
> at least your code will ship in just 2 more weeks. I think it'd be nice
> to keep the consistency, even over the jam-packed end-of-year.
>
> However, it seems entirely reasonable that the amount of code we
> actually ship is less, since so many things get in the way. We could
> expect the trains to be quite empty. And thus, any repo that doesn't
> have any changes, we can ignore for shipping.
Given no replies arguing in favour of a change, let's go with "leave the
trains alone" and cut trains on their regular schedule for the remainder
of the year. (With the understanding that John and Jon can only deploy
them as their bandwidth allows, of course!)
Cheers,
Ryan
> On Tue, Nov 1, 2016 at 9:03 PM Ryan Kelly <[email protected]
> <mailto:[email protected]>> wrote:
>
> On 2/11/16 14:52, Ryan Kelly wrote:
> >
> > * We should consider our train schedule over the December period, and
> > whether we want to alter it to account for Thanksgiving, Mozloha,
> > AWS re:Invent, the Holidays, and the New Year. I'll send a separate
> > email to discuss.
>
> If we leave them unaltered, the dates for cutting out upcoming trains
> are as follows:
>
> * train-73: 01 November
> * train-74: 14 November
> * train-75: 28 November
> * train-76: 12 December
> * train-77: 26 December
> * train-88: 09 January
>
> But we've got quite a lot of disrupted scheduled coming up:
>
> * The US thanksgiving weekend is 24th November
> * Our Ops folks will be out at AWS:reinvent week of 28th November
> * We're all in Hawaii week of 5th December
> * Several of us are taking leave after Hawaii as well
> * The holiday season kicks in in late December
>
> So does it make sense to shorten or lengthen or skip some of these
> trains? Or should we just keep them all on schedule and accept that
> they may be smaller than usual, or deployed a little layer?
>
> In particular, I'm thinking it probably doesn't make sense to cut
> train-75 at the start of the week of AWS:reinvent when :jrgm and :jbuck
> most likely won't have the bandwidth to deploy it. Perhaps we can save
> it up and deploy while we're all together in Hawaii?
>
>
> Cheers,
>
> Ryan
> _______________________________________________
> Dev-fxacct mailing list
> [email protected] <mailto:[email protected]>
> https://mail.mozilla.org/listinfo/dev-fxacct
>
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
