==== Current state 2022-07-18
- Description added; to be refined in pairing with Anne
==== Background/Goal
In a June 29 Slack thread, @AnneT and @SimoneThisDot surfaced a risk with regard to our current Codex release communications:
> End users do not have a way to understand how to solve breaking changes. The information provided in the changelog (this was raised as Abstract reached out as they had no idea what to do to fix the breaking changes). Maybe we should have an “breaking changes page” in the documentation.
We discussed a need to add some rigor around our Codex release communications process.
===== User stories
As a contributor, given that I have implemented Codex in my project, I want to access and understand changes to Codex as they are released, particularly "breaking" changes, so that I can take action if needed.
===== Considerations
- T311630 has also been raised; considering this out-of-scope for this task.
===== Acceptance criteria
[] MVP Codex release communication plan template for Codex releases has been drafted
[] Template has been reviewed by Design Systems team
[] Feedback has been solicited from current partner teams (Abstract Wikipedia, Growth, Web, WMDE)
[] MVP Codex release communication plan template has been added to https://www.mediawiki.org/wiki/Design_Systems_Team, as a section or subpage
===== Open questions
- Where should these release notes live? On the docs site would be nice; easy to link to and we could keep a running list for posterity
- How should we announce releases internally for now? Posting in #design-systems-engineering and perhaps #talk-to-design-systems-team?
- When do we switch over to a wider announcement process; e.g. sending release notes to mailing lists? Beta release? 1.0.0?