-
Notifications
You must be signed in to change notification settings - Fork 339
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
Draft comms for v4.0.0 release #2331
Draft comms for v4.0.0 release #2331
Comments
Have added draft announcement to page 6 of the 4.0 release comms doc. @calvin-lau-sig7 Can I get a review? :) |
@vanitabarrett @calvin-lau-sig7 I've also added a draft update for the 'Whats new' panel into the 4.0 release comms doc. Let me know how that looks, and when we're happy with it, I'll raise a PR that we can hold off merging till the right time. :) |
Thanks @EoinShaughnessy , looks good! Do we need to draft an email in Mailchimp too? |
@vanitabarrett Cheers for reviewing! Yep, we do - I haven't used Mailchimp before, but I can draft the email and then find out how. |
@vanitabarrett @calvin-lau-sig7 Hi! Have drafted an email message - it's on page 7 of the release comms doc. Feedback welcome! :) |
All looks great @EoinShaughnessy, nice one! |
@calvin-lau-sig7 Cheers for reviewing! Yeah, that'd be magic, thanks! |
What
Tell users about release of Frontend v4.0.0. This is a breaking release, so we need to be careful how we communicate these changes to users.
Why
So users know what changes have been released and where to look to find out what they might need to do.
How
On Design System homepage:
On Github:
On Slack, post message on:
On email, send to list:
Who needs to know about this
Content Design
Done when
The text was updated successfully, but these errors were encountered: