GitLab Migration - Migrate Project Releases - Milestone attribute

Proposed Solution

• For each migrated Project, migrate Project Releases.

Additional details

• Releases are based on (git) Tags and can be associated with 0, 1, or many Milestones.
• GitLab automatically generates zip, tar.gz, tar.bz2, and tar archived source code from the given Git tag. These are read-only assets.
• Users can add additional assets which are just links with a description (text).
• Releases have a released_at date/timestamp that would need to be preserved.

Links:

• GitLab documentation about Releases: https://docs.gitlab.com/ee/user/project/releases/
• GitLab Releases API: https://docs.gitlab.com/ee/api/releases/index.html#create-a-release

Iteration

Migrate Release:

• Milestone
• The "Evidence collection" asset

This information is retrievable from the Release API

Documentation

Following documentation should be updated with the objects/fields added in this issue:

• User docs: https://docs.gitlab.com/ee/user/group/import/
• Dev docs: https://docs.gitlab.com/ee/development/bulk_import.html

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.