Add helper text on how items in existing create from commit, tag, or branch drop-down are populated
Problem to solve
Users want to be able to associate branches, commits, and tags to releases - which we support. It is not clear though, how those items are populated or what is the latest branch/commit/tag.
Intended users
User experience goal
A user would be able to select a branch to associate with a Release in the release page.
Use case
The use case is for on-prem, legacy style deployments where people are building on a specific release branch that gets released to a target. Thinking about single tenant application distribution. Also, at GitLab we have a release branch that gets cut for Self Managed, in our own dogfooding use case we could tie MRs to the release which is from the branch that was cut anywhere from the 16th-18th
Proposal
TBD
Documentation
- We would need documentation for release branches
- We would want to consider a blog as well
What does success look like, and how can we measure that?
- We need to add documentation that commits and branches can have releases associated with them
What is the type of buyer?
Edited by Jackie Porter