Our attempt to deploy the new beta feature in T351339 failed, specifically because all beta features must be in an allow list (step 11 on the release requirements)
We should talk to the product owner for beta features (@Jdforrester-WMF) about the checklist. It seems many of these have been done already but.
Checklist
- Have a quick chat with the product owner for Beta Features (currently James Forrester)
- Make an extension (Not relevant as it is part of Vector)
- Get preliminary design review (The feature has gone through the design team)
- Get preliminary security review (I assume this can be done post-deploy if needed)
- Get preliminary performance review (I assume this can be done post-deploy if needed)
- Make sure there is a wiki page on MediaWiki.org for it that is understandable to the general public (https://www.mediawiki.org/wiki/Reading/Web/Accessibility_for_reading)
- Ensure that the talk page for the project is using Flow (JR: seems outdated?)
- Make sure there is someone on point for feedback, acting as a product manager (either volunteer or WMF staff) -- for community feedback, that person is @sgrabarczuk
- Make a Phabricator project for the extension FY2023-24-WE 2.1 Typography and palette customizations
- Enable the "final version" of the code on Beta Cluster at least a week before you want to go for production. (has been enabled for several weeks
- Make gerrit change (do not merge) to the Beta Features whitelist in mediawiki configuration
- Deploy!
Suggested todo
- Go through checklist with James. Make any updates to the feature as needed.
- Backport any changes
- Work with James to get a patch written.
- Identify if BetaFeatures should have a new product owner.