Move support branches docs to team docs

The process for using a support branch is being moved into our team docs as part of alphagov/design-system-team-docs#21. Remove the existing documentation and add a reference to it in our standard docs on publishing releases.
alphagov · Sep 20, 2023 · 3a73e8c · 3a73e8c
1 parent 1011e84
commit 3a73e8c
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 129 deletions.
diff --git a/docs/releasing/publishing-from-a-support-branch.md b/docs/releasing/publishing-from-a-support-branch.md
diff --git a/docs/releasing/publishing.md b/docs/releasing/publishing.md
@@ -2,6 +2,11 @@
 
 Read the docs for [what to do before publishing a release](/docs/releasing/before-publishing-a-release.md) to ensure you are prepared to publish.
 
+See the [documentation on support branches](https://govuk-design-system-team-docs.netlify.app/how-we-work/version-control/support-branches.html#support-branches) if you need to:
+
+- publish a new release of previous major versions of GOV.UK Frontend
+- publish a ‘hotfix’ release of GOV.UK Frontend without including other unreleased changes on the `main` branch
+
 # Publish a new version of GOV.UK Frontend
 
 Developers should pair on releases. When remote working, it can be useful to be on a call together.