Make sure your local unstable is up-to-date: git checkout unstable & git pull.Make sure your local master is up-to-date: git checkout master & git pull.Since there can be conflicts, it's easiest to use the 'ours' strategy which will allow you to use the state of unstable as-is (i.e. If you are making a feature release, you need to merge unstable onto master.If you are making a patch release, you can just release master with its new patches.Current releases are based on the master branch: git checkout master.Follow the remaining ordinary release steps (step 5 and onward).This ensures that npm lists the current version as the latest one. For patch releases, do the back-port patch release before the corresponding current release.Each milestone should contain its corresponding issues and pull requests. Ensure that milestones exist for the releases that you would like to make.Ensure the docs are updated with the list of releases you would like to make in documentation/md/intro.md (on both master and unstable branches).benchmark:single : run benchmarks only for the suite specified in benchmark/single.npm run test:modules -g "my test name" runs modules tests on only the matching test cases.test:modules : run unit tests on private, internal API.npm run test:build -g "my test name" runs build tests on only the matching test cases.npm run build should be run beforehand on a recent version of node.test:build : run the mocha tests on the public API of the lib (on a built bundle).npm run test:js -g "my test name" runs tests on only the matching test cases. ![]()
0 Comments
Leave a Reply. |