added ability to release as @next from master

[gkatsev]

Here's the output of contrib release next minor:

$ contrib release next minor --dry-run

DRY RUN OF release next minor

STEP 1. Ensure there's no unadded changes
$ git diff --exit-code

STEP 2. Ensure there's no uncommitted changes
$ git diff --cached --exit-code

STEP 3. Switch to the development branch
$ git checkout master

STEP 4. Get any changes to master in the main project
$ git pull upstream master

STEP 5. Create a temporary branch for the dist
$ git checkout -b temp-release-branch master

STEP 6. Bump package versions
$ grunt version:{{release_type}}

STEP 7 (ID: version). Return the current VJS Version from the package.json file
$ ./build/bin/version

STEP 8. Add and commit the package changes
$ git commit -am 'v{{version}}'

STEP 9. Checkout the developmet branch
$ git checkout master

STEP 10. Merge package changes into the dev brach
$ git merge temp-release-branch

STEP 11. Push the dev branch changes to the repo
$ git push upstream master

STEP 12. Checkout the temp branch again
$ git checkout temp-release-branch

STEP 13. Build the dist
$ grunt dist

STEP 14. Add the (otherwise ignored) release files
$ git add dist --force

STEP 15. Commit the dist changes
$ git commit -m 'v{{version}} dist'

STEP 16. Tag the release
$ git tag -a v{{version}} -m 'v{{version}}'

STEP 17. Push the new tag to the repo
$ git push upstream --tags

STEP 18. Publish to npm as 'next'
$ npm publish --tag next

STEP 19. Checkout the developmet branch
$ git checkout master

STEP 20. Delete the temp release branch
$ git branch -D temp-release-branch


IT'S OVER!

Fixes #2868

[gkatsev]

basically, what used to be under prerelease was moved into run_next, then prelease and next {patch, minor, major} use run_next which just picks up the appropriate release_type.

[misteroneill]

LGTM

[dmlap]

LGTM