PD 13.6 Planning Issue
🚀
Internal Milestone 13.6 Review & Discussion 13.6 Milestone: 2020-18-10 to 2020-17-11
Theme and/or Goal
- Automation - EC2 to autoDeploy & Auto stop environment
- Deployment (pipeline) visibility - Setting deployment weights through UI & Review App for child/forked pipeline
🌴
Holidays Please order by From date
Person | From | To |
---|---|---|
@agulina | 5 Nov | 6 Nov |
📦
Capacity Last 3 Milestones: @csouthard to fill out
-
Average MRs completed: (47 + 28 + 63) / 3 = 46
-
Average MRs per Engineer: (6 + 2.7 + 8.6) / 3 = 5.7 (Q3 Goal 10)
Stats derived from here: https://app.periscopedata.com/app/gitlab/556687/CI-CD-Section-Metrics
🦊
Deliverables Top priority deliverables:
~"Release::P1"
Issue | Weight | |
---|---|---|
Migrate postgresql from stable Helm repo (which is going away Nov 13, 2020) | 3 | |
Set Auto-Stop Environment Expiry Period when an environment is created | 1 | new |
Set deployment Traffic Weight via UI UX | 3 | new |
Auto Deploy to EC2 | 1 | new |
3 | possible spillover / in dev | |
Automatic rollback in case of failure | 3 | probable spillover / ready for dev |
~"Release::P2"
Issue | Weight | |
---|---|---|
Review app (dynamic environment) created from child pipeline does not show up in merge requests. | 1 | new |
Instrument AMAU of Canary Rollouts - Usage Ping | 2 | new |
Forward deployment - warn users on "Retry" UX | 1 | new |
Duplicate instances in deploy board | 1 | possible spillover / in dev |
none | possible spillover / unplanned / in dev | |
? | unlikely spillover / verification | |
3 | probable spillover / ready for dev |
~"Release::P3"
Issue | Weight | |
---|---|---|
Add documentation for CI/CD Using Gitlab CI And Amazon AWS S3 deployment UX | 1 | new |
|
2 | new |
Add ability to copy Feature Flag user list to clipboard UX | 3 | new |
Update environments list page / deploy board to be more legible | 1 | possible spillover / in dev |
Create job to stop ECS review Apps | 2 | probable spillover / in dev |
Remove repeated legend deployboard | 1 | probable spillover / ready for dev |
IDOR-Get feature flag user list (including user IDs) of any private/public projects | 1 | probable spillover / ready for dev |
Eliminate the difference between CE/EE for protected branches and protected environments and allow to restrict by users, in addition to by roles | 2 | Blocked |
🕵
Research - Needs Weight Issue - gitlab-org/gitlab#254191 (closed)
🎢
User Experience
🐛
Bug Fixes Top bugs:
🔒
Security Fixes Top security Issues:
💼
Technical Debt
gitlab-org/gitlab-ui#994 (closed)
🖌
User Experience Debt
Total weight: 37
🎯
OKR Alignment - Progressive Delivery Quarterly goal
- Product Manager complete 2 Validation Cycles - gitlab-com/Product#730 (closed)
- Product Manager completed projected Maturity
- Design OKR - Conduct 5 user research sessions for the UX Maturity Scorecard to evaluate the experience of Release Orchestration gitlab-com/www-gitlab-com#6201 (closed)
- Engineering OKRs (CI/CD)
👀
Things to Pay Attention To
Planning Tasks
-
Team updates holidays section -
EM update capacity section -
PM highlights work for Deliverables, User Experience, Bug Fixes, Security Fixes, Technical Debt sections -
PM describes how this milestone aligns with our team's OKRs -
Team highlights Things to Pay Attention To section -
Engineers begin working on issues in workflow::ready for development
Adjacent Planning Issues
Edited by Orit Golowinski