Test v4.0.0 pre-release and release notes with users

[vanitabarrett]

What

Once we have completed the majority of the work for v4.0.0, we should create a pre-release which we can share with users and get them to test out the update process and release notes.

Why

So that we can identify any issues with the release / release notes early and fix them before we do the actual release.

Who needs to know about this

Developers; Tech Writer; User Research

Dependent On

• The majority of the changes being included in v4.0.0 being finished
• The v4.0.0 release notes being complete

Done when

• Drafted comms for sharing the pre-release. Point people to the pre-release and the release notes
• Include a deadline for feedback?
• We have generated a pre-release for v4.0.0
• We have shared the pre-release with our users
• We have actioned any feedback

[calvin-lau-sig7]

Will promote and link to sign-up form to recruit participants as part of https://github.com/alphagov/design-system-team-internal/issues/516

[EoinShaughnessy]

In the comms (Slack message) for the pre-release, where should we tell users to leave feedback? In a Slack thread?

[EoinShaughnessy]

Rough draft of pre-release comms: https://docs.google.com/document/d/1HEAVQZBVOVOvsVqMlwtxbNySS31-B0Iu8X6ZT93fyFc/edit#

[EoinShaughnessy]

Feedback from users. No changes requested, but worth retaining for evidence of how they use notes and what they like.