From 873e766d2e0e936ddd6306eea3baf4bf016c1d41 Mon Sep 17 00:00:00 2001 From: Michael Krasnyk Date: Sun, 18 Mar 2018 13:55:30 +0100 Subject: [PATCH] Add Github releases step --- docs/releasing.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/releasing.md b/docs/releasing.md index 8fcf596e9..efe78ddde 100644 --- a/docs/releasing.md +++ b/docs/releasing.md @@ -48,8 +48,11 @@ We may introduce forward-compatible changes: query parameters and response prope 5. Use an annotated tag to mark the release: `git tag vx.y.z -a` Body of the tag description should be the changelog entries. 6. Use `npm run docs` to generate the API documentation. Copy `build/docs/*` to `https://github.com/Project-OSRM/project-osrm.github.com` in the `docs/vN.N.N/api` directory 7. Push tags and commits: `git push; git push --tags` -8. If not a release-candidate: Write a mailing-list post to osrm-talk@openstreetmap.org to announce the release -9. Wait until the travis build has been completed and check if the node binaries were published by doing: +8. On https://github.com/Project-OSRM/osrm-backend/releases press `Draft a new release`, + write the release tag `vx.y.z` in the `Tag version` field, write the changelog entries in the `Describe this release` field + and press `Publish release`. +9. If not a release-candidate: Write a mailing-list post to osrm-talk@openstreetmap.org to announce the release +10. Wait until the travis build has been completed and check if the node binaries were published by doing: `rm -rf node_modules && npm install` locally. -10. For final releases run `npm publish` or `npm publish --tag next` for release candidates. -11. Bump version in `package.json` to `{MAJOR}.{MINOR+1}.0-latest.1` on the `master` branch after the release. +11. For final releases run `npm publish` or `npm publish --tag next` for release candidates. +12. Bump version in `package.json` to `{MAJOR}.{MINOR+1}.0-latest.1` on the `master` branch after the release.