Deployment as opt out feature
Before deployment
- Community socializing; T280390 Finished: 30 July 2021
- Prepare code for deployment; owners @matmarex and @DLynch
- T269033 T282204 T277371 T282205
- Update QA ticket with a basic workflow for the release candidates; specify platforms, devices and wikis as well anything else to focus on @ppelberg
- See: T285726#7234271. Testing of specific workflows (e.g. edit notices) will happen in their respective implementation tickets (e.g. T269033).
- Beta feature usage analysis: T263053 @MNeisler
- Design review and sign off; owner @iamjessklein ETA: T274832 T288556 T287779 T288741 T289354
QA
- Once all subtasks are closed, make sure that the QA tasks are moved to the QA Board @LZaman
- QA All High Priority New Discussion Tool-related tickets will be tested @Ryasmeen @EAkinloose ETA: TK *Caveat: can not say for certain until we know how many tickets there will be to verify T288275 T288267 T285726
Deployment
- Deployment train or backport determined and coordinated by engineering team; owners @matmarex and @DLynch T285724 Targeted ETA: Tuesday, 14 September 2021
Post-deployment
- Publicize feature's availability at partner wikis; T280389
- Post updates to MediaWiki project page; owner @ppelberg
- Done in diff=4809513.