On 14/07/2016 14:23, John Morrison wrote: > On 07/13/16 15:19, Ryan Kelly wrote: >> >> On 14/07/2016 02:55, Sean McArthur wrote: >>> I was thinking of doing this off-cycle, i.e., get train-X live, >>> and then >>> re-test/ship train-X with node4x a couple of days later, so changes >>> in any >>> metrics/behaviours can be attributed to either the released >>> code, or to >>> the node4 runtime. >>> >>> >>> This was exactly what I was alluding to with my questions, and I pushed >>> slightly for this option in the meeting yesterday, for the same reasons: >>> to reduce the things that could blow up at the same time we upgrade to >>> node4. >> Sounds sensible to me. So let's amend the proposal to: get train-66 >> live, and then re-test/ship train-66 with node4x a couple of days later. >> > I was even thinking of doing after train-65 goes live, if things are all > chill and stuff.
This would also be fine ;-) Ryan _______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
