github/kata-containers
1
0
Fork 1
mirror of https://github.com/kata-containers/kata-containers.git synced 2025-06-29 08:47:56 +00:00
Code Issues Projects Releases Wiki Activity

improvement: docs: Update release documentation

Browse Source 
- Add information about package testing pipelines

- Fix release notes command

Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>
This commit is contained in:
Jose Carlos Venegas Munoz 2019-03-22 13:44:13 -06:00
parent 891692b6a6
commit 0a5b917c92
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
release/release.md
View File

@ -104,19 +104,29 @@ $ git pull
$PUSH=1 OBS_SUBPROJECT="releases:$(uname -m):${BRANCH}" ./build_from_docker.sh ${NEW_VERSION} $PUSH=1 OBS_SUBPROJECT="releases:$(uname -m):${BRANCH}" ./build_from_docker.sh ${NEW_VERSION}
``` ```
6. Create release notes: 6. Test packages
After all the packages have built succesfully (see status in OBS web page: https://build.opensuse.org/project/subprojects/home:katacontainers),
make sure the packages install and work. To help with this you can use the [package test job](http://jenkins.katacontainers.io/job/package-release-testing)
7. Create release notes:
```bash ```bash
$ cd ${GOPATH}/src/github.com/kata-containers/packaging/release $ cd ${GOPATH}/src/github.com/kata-containers/packaging/release
# Note: OLD_VERSION is where the script should start to get changes. # Note: OLD_VERSION is where the script should start to get changes.
$ ./runtime-release-notes.sh OLD_VERSION ${NEW_VERSION} > notes.md $ ./runtime-release-notes.sh OLD_VERSION ${NEW_VERSION} > notes.md
# Add the release notes in GitHub runtime. # Add the release notes in GitHub runtime.
$ hub -C "${GOPATH}/src/github.com/kata-containers/runtime" release edit -F notes.md $ hub -C "${GOPATH}/src/github.com/kata-containers/runtime" release edit -F notes.md "${NEW_VERSION}"
``` ```
7. Announce release: 7. Announce release:
Publish in [Slack and Kata mailing list][join-us-kata] that new release is ready. Publish in [Slack and Kata mailing list][join-us-kata] that new release is ready.
8. Send changes to upstream.
If you found any issue during the release process and you fix it, please send it back.
After your changes are merged, tag kata packaging with `${NEW_VERSION}` to identify the code used for the release.
[release-process-definition]: https://github.com/kata-containers/documentation/blob/master/Releases.md [release-process-definition]: https://github.com/kata-containers/documentation/blob/master/Releases.md
[release-checklist]: https://github.com/kata-containers/documentation/blob/master/Release-Checklist.md [release-checklist]: https://github.com/kata-containers/documentation/blob/master/Release-Checklist.md
[join-us-kata]: https://github.com/kata-containers/community#join-us [join-us-kata]: https://github.com/kata-containers/community#join-us