## Research objective This study was developed to help the Releases team evaluate the proposed design improvements (prototypes) to the Releases workflow. ## Methodology We ran an moderated test via Zoom calls with a total of 3 participants, both internal and external customers that currently use GitLab Releases as part of their workflow. ### Participant 1 * Engineering Manager @ GitLab. Lead a team responsible for GitLab releases and also continuous deployment. * 1 1/2 years in the current role (officially), 7 years unofficially. 15+ years in IT. * Create multiple releases a day automatically, have a monthly cadence for feature releases, multiple patch and security fix releases for multiple instances of GitLab (dot-com, dot-org. ops). * Top 3 tasks: * Making sure that the releases can be created, are safe, and operational. * Making sure the customers receive the updates in a timely manner. ### Participant 2 * BE engineer for the verify stage * Is the release manager of GitLab Runner from time to time, user of the Releases page. * 4 years with GitLab. * Develops code, review other people's code, when dealing with releases is mostly through the API (tags, attach some links to reg container, change jobs, so users will have all data) * Uses the release page constantly, links to it manually. ### Participant 3 * Software Engineer, 9 years in current role. * Works for an audio and communication manufacture company. * Top 3 tasks are: 1) maintain existing firmware, make sure it's build, reproducible, and available. 2) Maintain the test software, production machines, test software. 3) Look for new fun things to do and ideas to apply to their processes, like devops and CD. * Uses GitLab to store code, deploy to the website, firmware updates for prototype projects, CI/CD. Try to do Releases with GitLab. * Tricky process to work with embedded development because can't always have a docker. * Share responsibilities with another team mate. ## Videos | Participant | Notes | Recording | | ------ | ------ | ------ | | Participant 1 | [see notes](https://docs.google.com/spreadsheets/d/1RvifkLpsQP4N3K_e_zT0yk_9BHAcp0i50p45Tt9fIqw/edit#gid=0) | [video recording](https://drive.google.com/open?id=1FkJnRBw0ApvqxdiCJ-fkjlMaLCo-KZvx) | | Participant 2 | [see notes](https://docs.google.com/spreadsheets/d/1RvifkLpsQP4N3K_e_zT0yk_9BHAcp0i50p45Tt9fIqw/edit#gid=917081220) | [video recording](https://drive.google.com/file/d/1fFGVwkTc6PZlNRsqKvrUNk6zIbzvCYgg/view) | | Participant 3 | [see notes](https://docs.google.com/spreadsheets/d/1RvifkLpsQP4N3K_e_zT0yk_9BHAcp0i50p45Tt9fIqw/edit#gid=408327724) | [video recording](https://drive.google.com/open?id=1AvASbcerqZSqB5axQFw19nlFs8iV9RkQ) | ## Links * Research request issue https://gitlab.com/gitlab-org/ux-research/issues/754 * [Discussion guide](https://docs.google.com/document/d/1K8fn3Gq5C1E41OVoRQj76AAlJqGq7dUwtqEV2EWtcQI/edit?usp=sharing) * [Interview notes](https://docs.google.com/spreadsheets/d/1RvifkLpsQP4N3K_e_zT0yk_9BHAcp0i50p45Tt9fIqw/edit#gid=0)