Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare release notes and comms for v5.9.0 #5718

Open
7 tasks
Tracked by #5706
calvin-lau-sig7 opened this issue Feb 11, 2025 · 0 comments
Open
7 tasks
Tracked by #5706

Prepare release notes and comms for v5.9.0 #5718

calvin-lau-sig7 opened this issue Feb 11, 2025 · 0 comments

Comments

@calvin-lau-sig7
Copy link
Contributor

calvin-lau-sig7 commented Feb 11, 2025

Release comms doc

Release notes to be created in release notes folder

What

Prepare:

  • Changelog and release notes
  • Release comms, including email and Slack messages

Headlines:

  • improved File upload component
  • deprecating the service name and navigation links in the GOV.UK header
  • use Service navigation instead

Why

We want to support service teams to use the new component, and migrate to using the Service navigation

Who needs to work on this

Content designer, technical writer, v5.9 lead (@domoscargin)

Who needs to review this

Involved squads

Done when

  • changelog entries gathered
  • changelog reviewed by technical writer with developers
  • changelog 2i review
  • release notes created from changelog
  • release comms drafted for various platforms
  • release comms reviewed by involved squads and finalised
  • comms platforms prepared ahead of release
@calvin-lau-sig7 calvin-lau-sig7 added the awaiting triage Needs triaging by team label Feb 11, 2025
@domoscargin domoscargin moved this to Backlog 🏃🏼‍♀️ in GOV.UK Design System cycle board Feb 12, 2025
@domoscargin domoscargin added 🚀 release comms and removed awaiting triage Needs triaging by team labels Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog 🏃🏼‍♀️
Development

No branches or pull requests

2 participants