add how-to-release description #75

This commit is contained in:
Tobias Schneck
2018-04-03 18:47:16 +02:00
parent 15714a6fc8
commit 2161100ec3
2 changed files with 23 additions and 0 deletions

View File

@@ -135,6 +135,9 @@ If you open some graphic/work intensive websites in the Docker container (especi
Thx @raghavkarol for the hint!
## How to release
See **[how-to-release.md](./how-to-release.md)**
## Contributors
At this point we want to thank all contributors, which helped to move this great project by submitting code, writing documentation, or adapting other tools to play well together with the docker headless container.

20
how-to-release.md Normal file
View File

@@ -0,0 +1,20 @@
# How to release
* Check if `changelog.md` is correct
* Check if all features are merged in dev and pushed
* Pull the latest `dev` images
.build/tag_image.sh dev 1.x.x --save
* Test if the latest `dev` build is usable
* Change the the `FROM` statement in Sakuli `Dockerfile` to `dev` tag (in separate branch) and run (after build on dockerhub) [`docker/.build/tag_image.sh --save`](https://github.com/ConSol/sakuli/blob/master/docker/.build/tag_image.sh)
* On success - push the tested `dev` images to dockerhub
.build/tag_image.sh dev 1.x.x
.build/tag_image.sh dev latest
* Merge `dev` branch to `master`
* Create a release on [github.com/ConSol/docker-headless-vnc-container/releases/new](https://github.com/ConSol/docker-headless-vnc-container/releases/new)
* Write a blog post for [labs.consol.de](https://labs.consol.de/)