mirrors/ceph-csi
1
0
Fork 0
mirror of https://github.com/ceph/ceph-csi.git synced 2024-11-22 22:30:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: update to current release tracking method

Browse Source 
Signed-off-by: Niels de Vos <ndevos@redhat.com>
This commit is contained in:
Niels de Vos 2020-04-17 10:40:09 +02:00 committed by mergify[bot]
parent a219b2f9d4
commit 7bdb42c14a
1 changed files with 13 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
docs/releases.md
View File

@ -56,19 +56,22 @@ The Release Owner must follow the following process, which is
designed to ensure clarity, quality, stability, and auditability designed to ensure clarity, quality, stability, and auditability
of each release: of each release:
- Raise an issue and assign to themselves. - [Create a new milestone](https://github.com/ceph/ceph-csi/milestones/new) to
track the progress of the release. Set the scheduled date for the release, or
update it later when a date is selected.
[new issue in this repository](https://github.com/ceph/ceph-csi/issues/new) - [Raise new issue in this
repository](https://github.com/ceph/ceph-csi/issues/new) to track the
This issue is used to track the progress of the release with maximum visibility. progress of the release with maximum visibility. Link the issue with the
milestone for the release.
- Paste the release checklist into the issue. - Paste the release checklist into the issue.
This is useful for tracking so that the stage of the release is visible This is useful for tracking so that the stage of the release is visible to
to all interested parties. This checklist could be a list of issues/PRs all interested parties. This checklist could be a list of issues/PRs tracked
tracked for a release. The issues/PRs will be labelled with release tag. for a release. The issues/PRs will be marked with the milestone for the
For example, a label called `1.0.0` ( for release version 1.0.0) can be release. For example, a milestone called `release-2.1.0` (for release version
attached to issues and PRs for better tracking release items. 2.1.0) can be linked to issues and PRs for better tracking release items.
- Once all steps are complete, close the issue. - Once all steps are complete, close the issue and the milestone.