Change Details

This task represents the work with developing the plan for releasing the [[ https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2022/Better_diff_handling_of_paragraph_splits | 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} | Wikidiff2 | // In Progress// | | | | | | |2. | {T324759} | Core and MobileFrontend| ✅ | | | | | The legend should only display on Desktop so they need to be hidden in Extension MobileFrontend hence the patch in MobileFrontend| |3. | {T330229} | Core and VE | | | | | |*`Dropdown task` must be released with other dropdown tasks.| |3. | {T331589}| Core and VE | | | | | |*`Dropdown task` must be released with other dropdown tasks.| |3. | {T332266} | Core and VE | | | | | |*`Dropdown task` must be released with other dropdown tasks.| |3. | {T332267}|Core and VE | | | | | |*`Dropdown task` must be released with other dropdown tasks.| | | {T327193}|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}|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}|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: [[ https://patchdemo.wmflabs.org/ | 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.

This task represents the work with developing the plan for releasing the [[ https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2022/Better_diff_handling_of_paragraph_splits | 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} | Wikidiff2 | // In Progress// | | | | | | |2. | {T324759} | Core and MobileFrontend| ✅ | | | | | 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} | Core and VE | | | | | |*`Dropdown task` must be released with other dropdown tasks.| |3. | {T331589}| Core and VE | | | | | |*`Dropdown task` must be released with other dropdown tasks.| |3. | {T332266} | Core and VE | | | | | |*`Dropdown task` must be released with other dropdown tasks.| |3. | {T332267}|Core and VE | | | | | |*`Dropdown task` must be released with other dropdown tasks.| | | {T327193}|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}|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}|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: [[ https://patchdemo.wmflabs.org/ | 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.

This task represents the work with developing the plan for releasing the [[ https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2022/Better_diff_handling_of_paragraph_splits | 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} | Wikidiff2 | // In Progress// | | | | | | |2. | {T324759} | Core and MobileFrontend| ✅ | | | | | The legend should only display on Desktop so they need to be hidden in Extension MobileFrontend hence the patch in MobileFrontendSince 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} | Core and VE | | | | | |*`Dropdown task` must be released with other dropdown tasks.| |3. | {T331589}| Core and VE | | | | | |*`Dropdown task` must be released with other dropdown tasks.| |3. | {T332266} | Core and VE | | | | | |*`Dropdown task` must be released with other dropdown tasks.| |3. | {T332267}|Core and VE | | | | | |*`Dropdown task` must be released with other dropdown tasks.| | | {T327193}|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}|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}|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: [[ https://patchdemo.wmflabs.org/ | 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.