Static Analysis Async MoSCoW 16.3 - Maintenance
We want to continue to refine our backlog using the MoSCoW prioritization process. In this milestone we will focus on refining both typebug and typemaintenance issues, with the former being tracked in Static Analysis Async MoSCoW 16.3 - Bug (#422140 - closed).
The goal is to determine what should be closed out of backlog. This is not an attempt to weight issues which comes later after we determine whether they are even worth doing. Take a look at Static Analysis Async MoSCoW 15.3 (#368540 - closed) for an example of how we've done this exercise in the past.
More information about this process can be found under the Static Analysis MoSCoW Process section in the handbook.
Rules
MoSCoW rating: (Must, Should, Could, Wont, ?, or Elsewhere).
Extra ratings:
- ? - I don't understand what this is or have an opinion (more explicit than an empty cell)
- Elsewhere - means to send elsewhere in the event we determine this to belong to another team.
- Participation is optional: as long as one person has started we can use an aggregate
- Each team member adds MoSCoW Rating
- [optionally] each team member opens new discoto thread if any issue requires discussion
- Open for 1 week (2023-08-22)
- After 1 week, @amarpatel will compile ratings into overall column. He may take liberties with discrepancies but advertise back here in case others wish to contest
- @amarpatel as DRI for typemaintenance will determine whether to accept overall rating or override.
The cutoff for whether to close out "Should"s vs "Could"s vs "Wont"s is TBD.
Review
Currently populated with Development department members, but if others wish to participate, please feel free to add column!
This list is generated via created_at ASC list of SAST \\\~type::maintenance without the \\\~SAST: Reviewed label
Auto-Summary 🤖
Discoto Usage
Points
Discussion points are declared by headings, list items, and single lines that start with the text (case-insensitive)
point:. For example, the following are all valid points:
#### POINT: This is a point* point: This is a point+ Point: This is a point- pOINT: This is a pointpoint: This is a **point**Note that any markdown used in the point text will also be propagated into the topic summaries.
Topics
Topics can be stand-alone and contained within an issuable (epic, issue, MR), or can be inline.
Inline topics are defined by creating a new thread (discussion) where the first line of the first comment is a heading that starts with (case-insensitive)
topic:. For example, the following are all valid topics:
# Topic: Inline discussion topic 1## TOPIC: **{+A Green, bolded topic+}**### tOpIc: Another topicQuick Actions
Action Description /discuss sub-topic TITLECreate an issue for a sub-topic. Does not work in epics /discuss link ISSUABLE-LINKLink an issuable as a child of this discussion
Last updated by this job
Discoto Settings
---
summary:
max_items: -1
sort_by: created
sort_direction: ascendingSee the settings schema for details.
Auto-Summary 🤖
Discoto Usage
Points
Discussion points are declared by headings, list items, and single lines that start with the text (case-insensitive)
point:. For example, the following are all valid points:
#### POINT: This is a point* point: This is a point+ Point: This is a point- pOINT: This is a pointpoint: This is a **point**Note that any markdown used in the point text will also be propagated into the topic summaries.
Topics
Topics can be stand-alone and contained within an issuable (epic, issue, MR), or can be inline.
Inline topics are defined by creating a new thread (discussion) where the first line of the first comment is a heading that starts with (case-insensitive)
topic:. For example, the following are all valid topics:
# Topic: Inline discussion topic 1## TOPIC: **{+A Green, bolded topic+}**### tOpIc: Another topicQuick Actions
Action Description /discuss sub-topic TITLECreate an issue for a sub-topic. Does not work in epics /discuss link ISSUABLE-LINKLink an issuable as a child of this discussion
Last updated by this job
Discoto Settings
---
summary:
max_items: -1
sort_by: created
sort_direction: ascendingSee the settings schema for details.
Auto-Summary 🤖
Discoto Usage
Points
Discussion points are declared by headings, list items, and single lines that start with the text (case-insensitive)
point:. For example, the following are all valid points:
#### POINT: This is a point* point: This is a point+ Point: This is a point- pOINT: This is a pointpoint: This is a **point**Note that any markdown used in the point text will also be propagated into the topic summaries.
Topics
Topics can be stand-alone and contained within an issuable (epic, issue, MR), or can be inline.
Inline topics are defined by creating a new thread (discussion) where the first line of the first comment is a heading that starts with (case-insensitive)
topic:. For example, the following are all valid topics:
# Topic: Inline discussion topic 1## TOPIC: **{+A Green, bolded topic+}**### tOpIc: Another topicQuick Actions
Action Description /discuss sub-topic TITLECreate an issue for a sub-topic. Does not work in epics /discuss link ISSUABLE-LINKLink an issuable as a child of this discussion
Last updated by this job
Discoto Settings
---
summary:
max_items: -1
sort_by: created
sort_direction: ascending
See the settings schema for details.