Prepare comms and content to support component release

[calvin-lau-sig7]

What

Prepare and plan for various pieces of content that will need to be published to support the release of the Password input component

Includes steps in Tasks before publishing a new release of GOV.UK Frontend

Draft document for Comms

Draft document for release notes

Why

We want to make sure that users know:

• that we've released the new component
• what to do to use it
• our rationale and decision-making
• our testing

Who needs to work on this

Content designer, tech lead

Who needs to review this

Wider squad

Done when

Draft

Tasks

Beta Give feedback

1. Changelog is up to date
2. Updated roadmap and 'What's new' messages drafted
3. Release notes for new version of GOV.UK Frontend drafted

Publish

Tasks

Beta Give feedback

1. Release notes published
2. Password input govuk-design-system-backlog#240 converted into 'current component' discussion with new pinned post, and status changed to 'published'
3. 'Second password rationale' posted in backlog discussion
4. Accessibility testing summary posted in backlog discussion
5. 'What's new' message updated
6. Roadmap updated

[querkmachine]

This has probably inadvertently ended up having a lot of overlap with the release issues alphagov/govuk-frontend#4875 and alphagov/govuk-frontend#4876.

This issue can probably be trimmed down to remove the duplication.

[calvin-lau-sig7]

I'll take the release issues you've raised as canon and close this as a duplicate – only thing I need to do is add the backlog-type posts as "channels" on #4975

[calvin-lau-sig7]

Duplicated by release tickets, as mentioned above.