cartodb/crankshaft
1
0
Fork 0
mirror of https://github.com/CartoDB/crankshaft.git synced 2024-11-01 10:20:48 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update RELEASE process

Browse Source
This commit is contained in:
Raul Marin 2017-11-23 09:38:07 +01:00 committed by Raúl Marín
parent cf46633f24
commit 4ab4eadec9
1 changed files with 15 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
RELEASE.md
View File

@ -4,33 +4,35 @@ The release process of a new version of the extension
shall be performed by the designated *Release Manager*. shall be performed by the designated *Release Manager*.
## Release steps ## Release steps
1. Make sure `develop` branch passes all the tests. * Make sure `develop` branch passes all the tests.
1. Merge `develop` into `master` * Merge `develop` into `master`
1. Update the version number in `src/pg/crankshaft.control`. * Update the version number in `src/pg/crankshaft.control`.
1. Generate the next release files with this command: * Generate the next release files with this command:
```shell ```shell
make release make release
``` ```
1. Generate an upgrade path from the previous to the next release by copying the generated release file. E.g: * Generate an upgrade path from the previous to the next release by copying the generated release file. E.g:
```shell ```shell
cp release/crankshaft--X.Y.Z.sql release/crankshaft--A.B.C--X.Y.Z.sql cp release/crankshaft--X.Y.Z.sql release/crankshaft--A.B.C--X.Y.Z.sql
``` ```
NOTE: you can rely on this thanks to the compatibility checks. NOTE: you can rely on this thanks to the compatibility checks.
TODO: automate this step [#94](https://github.com/CartoDB/crankshaft/issues/94) TODO: automate this step [#94](https://github.com/CartoDB/crankshaft/issues/94)
2. Update the [NEWS.md](https://github.com/CartoDB/crankshaft/blob/master/NEWS.md) file
1. Commit and push the generated files. * Update the [NEWS.md](https://github.com/CartoDB/crankshaft/blob/master/NEWS.md) file
1. Tag the release: * Commit and push the generated files.
* Tag the release:
``` ```
git tag -a X.Y.Z -m "Release X.Y.Z" git tag -a X.Y.Z -m "Release X.Y.Z"
git push origin X.Y.Z git push origin X.Y.Z
``` ```
1. Deploy and test in staging
1. Deploy and test in production * Deploy and test in staging
1. Merge back into develop * Merge `master` into **`stable`**
* Deploy and test in production
* Merge `master` into **`develop`**
## Some remarks ## Some remarks