2019-08-05 - Triage report for "group::serverless and paas"
Hi, @danielgruesso @DylanGriffith @timzallman
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.
Unscheduled ~feature (non-customer)
-
#64640 (moved) Support assigning a predefined subdomain for a serverless function / application ~"Serverless", ~"devops::configure", ~"feature", ~"group::serverless and paas" -
#64326 (moved) Allow serverless outbound traffic to external services by default ~"Serverless", ~"devops::configure", ~"feature", ~"group::serverless and paas" -
#62781 (moved) Explore using OpenFaaS as GitLab Serverless runtimes ~"Serverless", ~"devops::configure", ~"feature", ~"group::serverless and paas"
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 | ~"No severity" | |
---|---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 | 0 |
~P2 | 0 | 0 | 0 | 0 | 0 |
~P3 | 0 | 0 | 1 | 0 | 0 |
~P4 | 0 | 0 | 0 | 2 | 0 |
~"No priority" | 0 | 0 | 0 | 0 | 2 |
frontend ~bug with customer
Unscheduled-
#63534 (closed) Security impact of setimmediate.js ~"P3", ~"S3", ~"bug", customer, ~"devops::configure", frontend, ~"group::serverless and paas", security, security-set-milestone
frontend ~bug (non-customer)
Unscheduled-
#64764 (closed) Layout issue in serverless index empty state ~"Accepting merge requests", ~"Good for 1st time contributors", ~"Serverless", ~"bug", ~"devops::configure", frontend, ~"group::serverless and paas", operations, reproduced on GitLab.com
Unscheduled ~bug (non-customer)
-
#64671 (moved) Failed to create resources during deployment ~"Configure", ~"P4", ~"S4", ~"Serverless", ~"bug", ~"devops::configure", ~"group::serverless and paas" -
#64664 (moved) Unable to recognize service.yaml
connection refused ~"Configure", ~"P4", ~"S4", ~"Serverless", ~"bug", ~"devops::configure", ~"group::serverless and paas" -
#62907 (moved) Changing serverless cluster namespace has no effect on deployments ~"Serverless", ~"bug", ~"devops::configure", ~"group::serverless and paas"
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: