UNPKG

openhim-core

Version:

The OpenHIM core application that provides logging and routing of http requests

openhim.org

jembi/openhim-core-js

40 lines (25 loc) • 2 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
# How to do an OpenHIM-core release This page describes the steps to follow to do an OpenHIM release. Make sure you are on the `master` branch and it is fully up-to-date before beginning this process. 1. `npm version (major|minor|patch)` - choose one according to semver. 1. `npm publish` 1. `git push origin master` 1. `git push origin vx.x.x` - push the tag that step #1 created. 1. Create a [new github release](https://github.com/jembi/openhim-core-js/releases/new) using the tag created in step #1 above, that includes the release notes. 1. Build a debian package and upload it to launchpad. Follow the [instructions here](https://github.com/jembi/openhim-core-js/tree/master/packaging). 1. Build a rpm package, follow the [instructions here](http://openhim.readthedocs.io/en/latest/how-to/how-to-build-and-test-rpm-package.html). ## Support Releases From time to time a support release may be required for critical security issues or bugs. When this happens, a support branch should be created in order to support that particular version. If the branch doesn't exist, create it from the latest tag for a particular release: - `git checkout -b support-vx.y vx.y.z` else if the branch exists, simply check it out and continue from there - `git checkout support-vx.y` Ideally fixes should first be developed separately and merged into master. They can then be `cherry-picked` for the support release: - `git cherry-pick bd68fe1c8cf81cbef2169414ce8440a7a2c69717` Although this may not always be possible, in which case the fixes can be added manually. When all fixes have been applied, test thoroughly and create a new release as per normal: 1. `npm version (major|minor|patch)` - increment the patch version. 1. `npm publish` 1. `git push origin support-vx.y` 1. `git push origin vx.y.z` - push the new tag 1. Create a [new github release](https://github.com/jembi/openhim-core-js/releases/new) When a particular version is no longer supported, its support branch should be deleted.