Uh oh!
There was an error while loading. Please reload this page.
extraced decode-ref.js, add tests, add rc builds - #126
Conversation
377ae70 to
726602cCompareStarefossen
commented
Jul 4, 2015
Sticking to the semver specification; RC versions should be labeled |
rvagg
commented
Jul 5, 2015
Thanks for pointing that out @Starefossen, I hadn't noticed the dot separation of tags in the spec before tbh. Will adjust for rc.3. |
rvagg
commented
Jul 5, 2015
Actually, getting feedback from @ljharb here would be useful before jumping straight in. |
ljharb
commented
Jul 5, 2015
I'm fine with |
rvagg
commented
Jul 5, 2015
the existing builds have |
ljharb
commented
Jul 5, 2015
hmm - if both formats are there it's going to be a huge pain. As long as either the archive files themselves are all the same convention, across both existing and new releases, or the old releases don't exist in Basically I want to avoid having to code in support for more than one convention/format. |
726602c to
e1506b2Comparervagg
commented
Jul 13, 2015
I've gone ahead and adopted the Unfortunately node-gyp also needed the same treatment in |
e1506b2 to
ba5e075Comparemgol
commented
Sep 4, 2015
Just a quick update - it will be https://nodejs.org/download/rc/ now. |
allow for
v3.0.0-rc1type build numbers, this means we have to tag RC builds as such in the repo but that's a good idea anyway.