No strong opinion, but I'm leaning with Michael. Have there been examples of nested dependency version mismatches actually biting us that we are insistent on shrinkwrap?
For the record, last time I looked into this, npm commands were a bit limited when it comes to easily managing dependency updates in package.json. However, theres an open call for PR to add npm upgrade: https://github.com/npm/npm/issues/4471 -Michal On Fri, Sep 19, 2014 at 8:59 AM, Marcel Kinard <cmarc...@gmail.com> wrote: > Nope. This discussion is about tweaking our process going forward. I want > to get 3.6 live as soon as the voting is complete, which is happening in > the thread titled "[Vote] Tools Release 3.6.3-0.2.13". Hmm, there are no > other votes there yet besides mine. Folks, please review, vote, and let's > get this puppy out the door! > > On Sep 18, 2014, at 3:50 PM, Parashuram Narasimhan (MS OPEN TECH) < > panar...@microsoft.com> wrote: > > > Also a quick question. Will we be withholding the 3.6.* release till we > resolve this discussion? > >
