Yes, sooner is better. Faster. Safer. Does the node binary get bundled into the rpm? Does the upgrade need to be tied to a train? Is it just logistically the sanest approach?
On Tue, Jul 12, 2016, 10:26 PM Ryan Kelly <[email protected]> wrote: > > Hi All, > > > If I understand the landscape correctly, we have all the necessary > pieces ready to upgrade to node v4 in production, and we just need to > pick a time to push forward with the deployment. If so, then let's pick > a train to target a node v4 release. > > Based on nothing but it being the next available train, I propose that > we make train-66 the one to go live with node v4 in production. > > :jrgm (or anyone else for that matter!), thoughts? > > > > Cheers, > > > Ryan > _______________________________________________ > Dev-fxacct mailing list > [email protected] > https://mail.mozilla.org/listinfo/dev-fxacct >
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
