This task represents the work with developing the plan for releasing the Better Diff improvements
Release plan sequence
Below is a sequence in which we *plan* to offer the Better Diff improvements. As with all deployments, this plan might change depending on what emerges in the conversations within the team and volunteers at these projects.
Order | Task | Code (Core, VE, Wikidiff2) | Code-Review | QA Approved | PM Approved | Merged | Release Date | Notes | |
---|---|---|---|---|---|---|---|---|---|
1. | T324803: Better Diffs: Wikidiff2 revise algorithm | Wikidiff2 | In Progress | ||||||
2. | T324759: Inline Diff: Add legend and tooltips | Core and MobileFrontend | โ | โ | โ | May 1st week | Since the legend should only be displayed on Desktop, there's a patch that is associated to this task in MobileFrontend to hide the legend in Mobile version | ||
3. | T330229: Inline Switch: Add inline format toggle when wikidiff2 is installed | Core | โ | *Inline switch | |||||
3. | T331589: Inline Switch: VE should activate/deactivate inline format toggle | VE | โ | *Inline switch must be released with other inline switch tasks. | |||||
3. | T336712: Inline format: add logic to show legend when going from table to inline format | Core | *Inline switch | ||||||
3. | T336713: Diff-type preference: save diff-type user selection as a preference | Core | *Inline switch | ||||||
T327193: Two Column: Symbol and visual marker changes | Core and Wikidiff2 | Styles will be implemented in core and they need to be deployed before deploying the layout changes that will happen in Wikidiff2 | |||||||
T324761: Two Column: one or more lines added or removed markers | Core and Wikidiff2 | โ | CSS Styles, if needed, will be implemented in core and they need to be deployed before deploying the layout changes that will happen in Wikidiff2 | ||||||
T324755: Inline Diff: Update visual markers for text changes | Core and Wikidiff2 | CSS Styles, if needed, will be implemented in core and they need to be deployed before deploying the layout changes that will happen in Wikidiff2 | |||||||
Notes
- A feature flag would add an unnecessary effort that can be avoided if we release in the appropriate order and merged tasks once they been approved by QA and Product.
Requirements
- Before any work is merged, it needs to be approved by QA and product so that it's not release to users before being fully tested. We will take advantage of: patch demo, https://commtech.wmcloud.org/wiki/Main_Page, http://commtech-2.wmcloud.org/
- Every task will have it's own release plan. Tasks should not be merged until the Release Plan has been fulfilled. Ex: https://phabricator.wikimedia.org/T330229
Timing
- One purpose for this sequence is to allow users to face the improvements in the appropriate order.
Communication
- In Tech/News
- Announcement in #release-announcements Slack channel
Done
- A plan is documented on this ticket that lists the order in which tasks need to be released.