... | ... | @@ -4,7 +4,7 @@ |
|
|
* Make sure all customers and Turris team are ready for public disclosure.
|
|
|
* Coordinate unembargo date with [OSS distros mailing list](http://oss-security.openwall.org/wiki/mailing-lists/distros) and obtain CVE # from the list.
|
|
|
|
|
|
1. Create a branch name starting with `release`
|
|
|
1. Create a branch name starting with `release`
|
|
|
|
|
|
- Reason: There are special release-only CI checks that are executed for branch names starting with [`release`](https://gitlab.nic.cz/knot/knot-resolver/-/blob/57fd2fd453850e9c774023b22335378953af9edf/.gitlab-ci.yml#L183)
|
|
|
|
... | ... | @@ -52,9 +52,12 @@ |
|
|
- `mount /mnt/secure`
|
|
|
- `cp knot-resolver-X.Y.Z.tar.xz* /mnt/secure/knot-resolver`
|
|
|
|
|
|
1. Documentation should regenerate automatically: check http://readthedocs.org/projects/knot-resolver/builds/
|
|
|
|
|
|
1. ReadTheDocs documentation should regenerate automatically: check http://readthedocs.org/projects/knot-resolver/builds/
|
|
|
- If the tag isn't there, trigger the [webhook](https://gitlab.nic.cz/knot/knot-resolver/-/hooks) manually - Select `Test -> Tag push events` on the readthedocs hook
|
|
|
- *TODO: This mechanism may be superseded by the next step with GitLab CI*
|
|
|
|
|
|
1. Documentation should generate automatically as a CI job
|
|
|
- To put it on the main <https://knot.pages.nic.cz/knot-resolver> page, run the manual `docs:public` job.
|
|
|
|
|
|
1. Build docker image and push it to docker hub.
|
|
|
- In the git dir, make sure you have a clean repo and the proper tag checked out:
|
... | ... | @@ -114,4 +117,4 @@ |
|
|
- This deploys the version from ODVR repository to the test runners that are very similar to the production environment.
|
|
|
- If the playbook finishes successfully, it is safe to notify admins to deploy the new version.
|
|
|
|
|
|
1. Merge any changes and notify [Kryštof](<mailto:krystof.sadek@nic.cz>) about the new version. Include link to a MR if there have been any changes. |
|
|
\ No newline at end of file |
|
|
1. Merge any changes and notify [Kryštof](<mailto:krystof.sadek@nic.cz>) about the new version. Include link to a MR if there have been any changes. |