Skip to content

Commit d39e5df

Browse files
committed
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.
1 parent d5456e0 commit d39e5df

File tree

2 files changed

+5
-129
lines changed

2 files changed

+5
-129
lines changed

Diff for: docs/releasing/publishing-from-a-support-branch.md

-129
This file was deleted.

Diff for: docs/releasing/publishing.md

+5
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,11 @@
22

33
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.
44

5+
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:
6+
7+
- publish a new release of previous major versions of GOV.UK Frontend
8+
- publish a ‘hotfix’ release of GOV.UK Frontend without including other unreleased changes on the main branch
9+
510
# Publish a new version of GOV.UK Frontend
611

712
Developers should pair on releases. When remote working, it can be useful to be on a call together.

0 commit comments

Comments
 (0)