22 May 2020
Release:Progressive Delivery Group | GitLab
https://about.gitlab.com/handbook/engineering/development/ci-cd/release/progressive-delivery/
Product sections, stages, groups, and categories | GitLab
https://about.gitlab.com/handbook/product/categories/#progressive-delivery-group
PD 13.1 Planning Issue (#2) · Issues · GitLab.org / CI-CD / progressive_delivery · GitLab
https://gitlab.com/gitlab-org/ci-cd/progressive_delivery/-/issues/2
Show alerts in environment index page (#214634) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/214634
Offer in-product guidance for deploying to AWS (#207830) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/207830
Allow parent project's developers to create pipelines for merge requests for fork MRs (#217451) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/217451
Notifications for when pipelines are fixed (#24309) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/24309
A/B testing Problem Validation (#676) · Issues · GitLab.org / GitLab UX Research · GitLab
https://gitlab.com/gitlab-org/ux-research/-/issues/676
Progressive Delivery: Needs UX Review (&3357) · Epics · GitLab.org · GitLab
https://gitlab.com/groups/gitlab-org/-/epics/3357
Cancel deployment jobs when there is an alert on an environment (#216949) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/216949
Implement Blue/Green Switch on Deploy Boards (#218140) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/218140
Set deployment Traffic Weight via UI (#218139) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/218139
UX Department Performance Indicators | GitLab
https://about.gitlab.com/handbook/engineering/ux/performance-indicators/#ux-debt
https://about.gitlab.com/handbook/engineering/development/ci-cd/release/progressive-delivery/
Product sections, stages, groups, and categories | GitLab
https://about.gitlab.com/handbook/product/categories/#progressive-delivery-group
PD 13.1 Planning Issue (#2) · Issues · GitLab.org / CI-CD / progressive_delivery · GitLab
https://gitlab.com/gitlab-org/ci-cd/progressive_delivery/-/issues/2
Show alerts in environment index page (#214634) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/214634
Offer in-product guidance for deploying to AWS (#207830) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/207830
Allow parent project's developers to create pipelines for merge requests for fork MRs (#217451) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/217451
Notifications for when pipelines are fixed (#24309) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/24309
A/B testing Problem Validation (#676) · Issues · GitLab.org / GitLab UX Research · GitLab
https://gitlab.com/gitlab-org/ux-research/-/issues/676
Progressive Delivery: Needs UX Review (&3357) · Epics · GitLab.org · GitLab
https://gitlab.com/groups/gitlab-org/-/epics/3357
Cancel deployment jobs when there is an alert on an environment (#216949) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/216949
Implement Blue/Green Switch on Deploy Boards (#218140) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/218140
Set deployment Traffic Weight via UI (#218139) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/218139
UX Department Performance Indicators | GitLab
https://about.gitlab.com/handbook/engineering/ux/performance-indicators/#ux-debt
- 1 participant
- 6 minutes
22 May 2020
For all 13.1 Verify and Release kick-off videos:
13.1 Verify and Release UX Milestone Kick-off (#6) · Issues · GitLab.org / Verify and Release UX Team · GitLab
https://gitlab.com/gitlab-org/verify-and-release-ux-team/-/issues/6
Pages as shown in the video!
Verify:Continuous Integration Group | GitLab
https://about.gitlab.com/handbook/engineering/development/ci-cd/verify/continuous-integration/
Product sections, stages, groups, and categories | GitLab
https://about.gitlab.com/handbook/product/categories/#continuous-integration-group
13.1 Planning Issue (#3) · Issues · GitLab.org / CI-CD / continuous integration group · GitLab
https://gitlab.com/gitlab-org/ci-cd/continuous-integration/-/issues/3
Make pipeline permissions more controllable and flexible (#35067) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/35067
UI to browse locked artifacts (#217511) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/217511
CI linter should advise of errors/warnings/deprecations (#216444) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/216444
CI: Needs UX Review (&3374) · Epics · GitLab.org · GitLab
https://gitlab.com/groups/gitlab-org/-/epics/3374
Do not show `detached` label if it is not possible to run as `attached` (#217718) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/217718
UX Department Performance Indicators | GitLab
https://about.gitlab.com/handbook/engineering/ux/performance-indicators/#ux-debt
13.1 Verify and Release UX Milestone Kick-off (#6) · Issues · GitLab.org / Verify and Release UX Team · GitLab
https://gitlab.com/gitlab-org/verify-and-release-ux-team/-/issues/6
Pages as shown in the video!
Verify:Continuous Integration Group | GitLab
https://about.gitlab.com/handbook/engineering/development/ci-cd/verify/continuous-integration/
Product sections, stages, groups, and categories | GitLab
https://about.gitlab.com/handbook/product/categories/#continuous-integration-group
13.1 Planning Issue (#3) · Issues · GitLab.org / CI-CD / continuous integration group · GitLab
https://gitlab.com/gitlab-org/ci-cd/continuous-integration/-/issues/3
Make pipeline permissions more controllable and flexible (#35067) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/35067
UI to browse locked artifacts (#217511) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/217511
CI linter should advise of errors/warnings/deprecations (#216444) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/216444
CI: Needs UX Review (&3374) · Epics · GitLab.org · GitLab
https://gitlab.com/groups/gitlab-org/-/epics/3374
Do not show `detached` label if it is not possible to run as `attached` (#217718) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/217718
UX Department Performance Indicators | GitLab
https://about.gitlab.com/handbook/engineering/ux/performance-indicators/#ux-debt
- 1 participant
- 3 minutes
19 May 2020
Welcome to the 13.1 Release Management UX kickoff! I am Rayana Verissimo, Sr. Product Designer at GitLab.
The Release Management Team is responsible for the categories of Release Evidence, Release Orchestration, Secrets Management, and GitLab Pages. In 13.1 we are taking a moment to improve visibility into performance, enhancing the backstage and technical aspects of GitLab that support the Release Management features.
I will focus on working hands on with some frontend issues, in order to burn down the UX Debt that was part of our backlog. UX Debt means that for a given issue, we failed to meet defined standards for our Design system or for usability and feature viability standards as defined in agreed-upon design assets.
In parallel, I’ll be working on some of the Release Orchestration items that are currently in the workflow:design phase.
- https://gitlab.com/gitlab-org/gitlab/-/issues/195692
- https://gitlab.com/gitlab-org/gitlab/-/issues/212063
- https://gitlab.com/gitlab-org/gitlab/-/issues/199429
- https://gitlab.com/gitlab-org/gitlab/-/issues/214082
- https://gitlab.com/gitlab-org/gitlab/-/issues/196168
- More about UX Debt: https://about.gitlab.com/handbook/engineering/ux/performance-indicators/#ux-debt
The Release Management Team is responsible for the categories of Release Evidence, Release Orchestration, Secrets Management, and GitLab Pages. In 13.1 we are taking a moment to improve visibility into performance, enhancing the backstage and technical aspects of GitLab that support the Release Management features.
I will focus on working hands on with some frontend issues, in order to burn down the UX Debt that was part of our backlog. UX Debt means that for a given issue, we failed to meet defined standards for our Design system or for usability and feature viability standards as defined in agreed-upon design assets.
In parallel, I’ll be working on some of the Release Orchestration items that are currently in the workflow:design phase.
- https://gitlab.com/gitlab-org/gitlab/-/issues/195692
- https://gitlab.com/gitlab-org/gitlab/-/issues/212063
- https://gitlab.com/gitlab-org/gitlab/-/issues/199429
- https://gitlab.com/gitlab-org/gitlab/-/issues/214082
- https://gitlab.com/gitlab-org/gitlab/-/issues/196168
- More about UX Debt: https://about.gitlab.com/handbook/engineering/ux/performance-indicators/#ux-debt
- 1 participant
- 4 minutes
18 May 2020
Welcome to the 13.1 Release Management UX kickoff! I'm Lorie Whitaker, Staff UX Researcher at GitLab.
The Release Management Team is responsible for the categories of Release Evidence, Release Orchestration, Secrets Management, and GitLab Pages.
In 13.1, my research efforts will be focused on Merge Requests. I'll be diving into defining what poor performance looks like for various users as well as supporting the design teams who are making design changes to the MR process.
I'll also be working on defining JTBD across GitLab, in order to establish shared definitions of what JTBD are, how to create them and validate them, and how Product and UX should use them.
- MR - https://gitlab.com/gitlab-org/ux-research/-/issues/836
- JTBD - https://gitlab.com/gitlab-org/ux-research/-/issues/865
The Release Management Team is responsible for the categories of Release Evidence, Release Orchestration, Secrets Management, and GitLab Pages.
In 13.1, my research efforts will be focused on Merge Requests. I'll be diving into defining what poor performance looks like for various users as well as supporting the design teams who are making design changes to the MR process.
I'll also be working on defining JTBD across GitLab, in order to establish shared definitions of what JTBD are, how to create them and validate them, and how Product and UX should use them.
- MR - https://gitlab.com/gitlab-org/ux-research/-/issues/836
- JTBD - https://gitlab.com/gitlab-org/ux-research/-/issues/865
- 1 participant
- 2 minutes
21 Apr 2020
Going over Verify and Release UX work for the upcoming milestone to align on possible overlaps and dependencies between Product Designers.
- 6 participants
- 49 minutes