Updating the Website

To page describes how to update the website between releases.

As part of the release process we generate and publish the website. An (intentional) side-effect of this process is to create a branch for the release (that is, 2.1.0 or `3.1.0).

If we need to make a change:

  • make the change on master as normal (so that the docs will be there for the next release)

  • cherry-pick the changes onto these documentation branches.

Then publish as per the main release process:

Prereqs (software and doc tooling) are summarised in Appendix: Release Prereqs.