This is a metadata epic to track upcoming improvements to creating a Release with GitLab. ## Challenges Users now have the ability to create and edit releases through the UI. Before this feature was added, the only way to edit the details of an existing release was through the [Releases API](https://docs.gitlab.com/ee/api/releases/#update-a-release). ## Vision We should update the **New Release** page and the **Edit Release** page to support updating *all* information about a release that is currently supported in the API. This will effort bring us closer to maturity level: Viable. ## Focus Areas * Improve the user experience for Tags and Releases, by allowing users to manipulate data with GitLab in fewer steps. * Bring existing capabilities to the surface and empower release managers and non technical users to orchestrate releases by supporting advanced administration of Releases with GitLab. ## Activity/Deliverables * We will deliver both ~UX and ~frontend that will improve the current Create and Edit Release form to meet the same capabilities currently available in the API. * We will update the documentation for creating and updating a release https://docs.gitlab.com/ee/user/project/releases/index.html * Release links will be tackled under the Runbooks epic: https://gitlab.com/gitlab-org/gitlab/issues/9427 - Update: release links are complete! | Attribute | Is currently present on the UI? | Required | Description | |-----------|-----------|-------------|---------| | tag_name | :white_check_mark: | yes | The tag where the release will be created from. | | ref | :white_check_mark: | yes, if tag_name doesn’t exist | If tag_name doesn’t exist, the release will be created from ref. It can be a commit SHA, another tag name, or a branch name. | | name | :white_check_mark: | no | The release name. | | description | :white_check_mark: | no | The description of the release. You can use Markdown. | | milestones | :white_check_mark: | no | The title of each milestone to associate with the release ([] to remove all milestones from the release). | | released_at | | no | The date when the release will be/was ready. Expected in ISO 8601 format (2019-03-15T08:00:00Z)| | assets:links | :white_check_mark: | no | An array of assets links. | | assets:links:name | :white_check_mark: | required by: assets:links | The name of the link. | | assets:links:url | :white_check_mark: | required by: assets:links | The url of the link. | The one exception is the Release assets, which require a slightly different process for creation vs. updating because of the way our API is designed (details here: https://gitlab.com/gitlab-org/gitlab/issues/9427#note_295774016). So this data point will require a little extra work to enable when creating new Releases. ## Success metrics * After this epic is complete, creating a Release with GitLab should be easy. * Dogfooding: We will improve the workflow for creating Releases and Tags.