Skip to content

Latest commit

 

History

History
58 lines (37 loc) · 2.13 KB

docs-release-process.md

File metadata and controls

58 lines (37 loc) · 2.13 KB

Releasing a new version of the Knative documentation

This document describes how to perform a docs release. In general, this should be done by one of the release managers in the list at https://github.com/knative/release.

To release a new version of the docs you must:

  1. Check dependencies
  2. Create a release branch
  3. Generate the new docs version

Check dependencies

You cannot release a new version of the docs until the Knative components have built their new release. This is because the website references these releases in various locations.

Check the following components for the new release:

Create a release branch

  1. Check on the #docs Slack channel to make sure the release is ready. In the future, we should automate this so the check isn't needed.

  2. Using the GitHub UI, create a release-X.Y branch based on main.

branch

Generate the new docs version

To generate the new version of the docs, you must update the hack/build.sh script in the main branch to reference the new release.

We keep the last 4 releases available per our support window.

To generate the new docs version:

  1. In hack/build.sh on the main branch, update VERSIONS and RELEASE_BRANCHES to include the new version, and remove the oldest. Order matters, most recent first.

    For example:

    VERSIONS=("1.2" "1.1" "1.0" "0.26")
RELEASE_BRANCHES=("knative-v1.2.0" "knative-v1.1.0" "knative-v1.0.0" "v0.26.0")

  2. PR the result to main.

How GitHub and Netlify are hooked up

TODO: add information about how the docs are built and served using Netlify