2019-08-05 - Triage report for "group::release management"
Hi, @cstasik @darbyfrey @jhampton
This is a group or stage level triage package that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:
- https://about.gitlab.com/handbook/engineering/quality/guidelines/triage-operations/#current-packages
Scheduling the workload is a collaborative effort by the Product Managers and Engineering Managers for that group. Please work together to provide a best estimate on priority and milestone assignments. For each issue please:
- Determine if the issue should be closed if it is no longer relevant or a duplicate.
- If it is still relevant please assign either a best estimate versioned milestone, the %Backlog or the %Awaiting further demand milestone.
- Specifically for ~bug, if there is no priority or clarity on a versioned milestone, please add a Priority label. Priority labels have an estimate SLO attached to them and help team members and the wider community understand roughly when it will be considered to be scheduled.
- Once a milestone has been assigned please check off the box for that issue.
- Please work with your team to complete the list by the due date set.
Feature Proposal Section
For the following feature proposals. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.
customer
Unscheduled ~feature with-
#64446 (closed) Make release creation easy in CI pipelines customer, ~"devops::release", ~"feature", ~"group::release management", ~"release orchestration"
Unscheduled ~feature (non-customer)
-
#65177 (moved) Order of asset links in a release is not defined ~"Release", ~"devops::release", ~"feature", ~"group::release management" -
#65027 (moved) allow to opt-out from automated Environment stopping when a branch gets deleted ~"Release", ~"devops::release", environments, ~"feature", ~"group::release management", ~"release orchestration"
Bug Section
For the following bugs. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone and ensure that a priority label is set.
Heatmap for all bugs
~S1 | ~S2 | ~S3 | ~S4 | |
---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 |
~P2 | 0 | 3 | 0 | 0 |
~P3 | 0 | 0 | 2 | 0 |
~P4 | 0 | 0 | 1 | 1 |
~"No priority" | 0 | 0 | 1 | 0 |
Unscheduled ~bug (non-customer)
-
#65058 (moved) Pages hosted on gitlab.io have a broken TLS cert for some users ~"P2", ~"Release", ~"S2", ~"bug", ~"devops::release", ~"group::release management", ~"pages" -
#64776 (moved) Automatic Certificate Management with Let's Encrypt applies *.gitlab.io certificate during setup ~"Release", ~"S3", ~"bug", ~"devops::release", ~"group::release management", ~"pages", ~"release::validation::backlog" -
#63773 (moved) Project settings pages access control label misleading, fully disables pages ~"P4", ~"Release", ~"S4", UX, ~"bug", ~"devops::release", ~"group::release management", ~"pages", ~"release::validation::backlog" -
#62249 (moved) pages:deploy not getting triggered when using hidden pages job ~"P3", ~"Release", ~"S3", ~"bug", ~"devops::release", ~"group::release management", ~"group::release management", ~"pages" -
#61662 (moved) Gitlab.com Pages: Verification does not recongize txt entires for CNAME entries ~"P2", ~"S2", ~"bug", ~"devops::release", ~"group::release management", ~"missed-SLO", ~"pages"
Heatmap for ~missed-SLO bugs
~S1 | ~S2 | ~S3 | ~S4 | |
---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 |
~P2 | 0 | 1 | 0 | 0 |
~P3 | 0 | 0 | 0 | 0 |
~P4 | 0 | 0 | 0 | 0 |
This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook: