diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-27 15:06:30 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-27 15:06:30 +0300 |
| commit | 3269a20692c5b1f32862072d7897a4e753bae9ef (patch) | |
| tree | 9dfc6e7ccb857b323dc8b12259d339b76b8b90bf /doc/user/project/releases/index.md | |
| parent | c02f53288a838166a28518983fae3b80ca5936d8 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/project/releases/index.md')
| -rw-r--r-- | doc/user/project/releases/index.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/user/project/releases/index.md b/doc/user/project/releases/index.md index 8372aefc94c..9b7b20be98f 100644 --- a/doc/user/project/releases/index.md +++ b/doc/user/project/releases/index.md @@ -147,7 +147,7 @@ You can also edit an existing tag to add release notes: ## Release Evidence -> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/26019) in GitLab 12.5. +> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/26019) in GitLab 12.6. Each time a new release is created, specific related data is collected in parallel. This dataset will be a snapshot this new release (including linked @@ -155,7 +155,7 @@ milestones and issues) at moment of creation. Such collection of data will provide a chain of custody and facilitate processes like external audits, for example. The gathered Evidence data is stored in the database upon creation of a new -release as a JSON object. In GitLab 12.5, a link to +release as a JSON object. In GitLab 12.6, a link to the Evidence data is provided for [each Release](#releases-list). Here's what this object can look like: |