Release 14.2 Planning Issue

Internal Milestone 14.2 Review & Discussion 🚀

14.2 Milestone: 2021-07-18 to 2021-08-17

14.2 Theme:

  • Environments!
  • Follow up on the 🐛 bash Milestone

Plan Board

Schedule Board

Build Board

Capacity 📦

Last 3 Milestones:

  • Average MRs completed:
  • Average MRs per Engineer:

Deliverables 🦊

This includes all planned issues, including User Experience, Bugs, Security, Technical Debt, UX debt, Usability etc.

Top priority deliverables:

~"Release::P1"

Issue Weight Note
Cleanup Background Migration for Orphaned Deployments 1 Work started in 14.1, we should complete in 14.2 environments Category:Release Orchestration
Confidential 3 ~bug security
Expose deployment_tier in the “Pipeline events” webhook needs weight feels like a 1 environments
Add a simple link to read the release note needs weight feels like a 1 Category:Release Orchestration frontend
Manually renaming environments breaks future deployments 2 environments ~bug
Snowplow instrumentation for Environments frontend environments
Decide if environments/deployments should be part of CI database

~"Release::P2"

Issue Weight Note
Remove project and group releases json endpoints 2 ~bug Category:Release Orchestration
combo of "environment" and KUBERNETES_SERVICE_ACCOUNT_OVERWRITE does not work needs weight ~bug environments
Update Deployments::HooksWorker to utilize new Sidekiq read-only database replicas 1 Help improve Database performance by moving utilizing replicas
Clean up legacy Feature Flag Code needs weight Follow up to gitlab-org/gitlab#333459 (closed) Category:Feature Flags
Match Feature Flag API with Unleash Client Casing 3 ~bug Category:Feature Flags
Possibility to enforce the execution order of jobs using resource_group 4 Category:Continuous Delivery Resouce Groups
Distribute release-cli binaries as a generic package 1 Category:Continuous Delivery GitLab Release CLI security

~"Release::P3"

Issue Weight Note
Invalid Environment Not Being Created Should Be Surfaced To User ~bug generates lots of errors
CI resource_group not working when using $CI_ENVIRONMENT_NAME directly 1 ~bug Category:Continuous Delivery Resouce Groups
Allow per-site custom configurations 3 Category:Pages, Popular Improvement Request
Check that orphaned deployments do not occur 1 environments, follow-up to gitlab-org/gitlab#26229 (closed)
Address Technical debt with Environments environments Pick from things that are in this list

Total weight: XX

Research 🕵

14.2 Needs Weight Issue: #76 (closed)

Design 🌀

Issue Weight Note
✅ Allow setting GitLab Pages Access Control on Group level 2 Security-related, priority issue
✅ Invalid Environment Not Being Created Should Be Surfaced To User 2 Done!
✅ Start running Problem Validation – Environments Page 3 MR merged!
✅ Action Buttons in Environment page provide little context without labels 3 Done, ready for development!
🧊 Design new component to replace environments table 5 Blocked by problem validation
🧊 'Deploy to' label on environment is not necessarily right 2 Blocked by problem validation & design new component
🚗 Improve default sorting on Single Environment Page 3 Parked in favour of research issue
🚗 Manual deploy button used as ReDeploy button and without interval/restriction 3 Parked for later

Total weight: 17

✋ Not Started | 🧊 Blocked | 🚗 Parked | 🔄 In Progress | 🏓 In feedback or review | ✅ Done

Previous Design backlog
Issue Weight Note
Disable the option to archive/delete a project if there are active environments associated to it 2
Environments tracks the wrong deployment 3 Might track to gitlab-org/gitlab#292031 (closed) that is also related to sorting environments list
Environment folders in index page cause various UI misbehaviours 3 Might be similar to #300677, #28701 and #227034
Make timer for delayed jobs in environments list dynamic 3
'Deploy to' label on environment is not necessarily right 2 Might be UX ready, need to get more context
Allow setting GitLab Pages Access Control on Group level
Ongoing Design Work Notes Percent
UX Design for Release Milestone work: tactical design, research, implementation support 70%
UX Strategy for Release Mapping & defining long term vision for Release group 10%
Personal Growth / Design Community Career development, Pajamas contributions, coffee chats, sync and async cross-functional engagements 20%

OKR Alignment 🎯

#71 (closed)

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
Edited by Daniel Fosco