From d6568dc4c6758956f3dbbdcc28a0eae757c6c081 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Thu, 12 Jan 2023 09:08:00 +0100 Subject: [PATCH 1/4] Add release blocker WF --- README.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index c0bb168068..8704a94645 100644 --- a/README.md +++ b/README.md @@ -2,8 +2,24 @@ Holds generated but persistent results from building the `ansible` community package. This information may be referred to by other projects and scripts. +## Milestones + Release engineers check the [milestones](https://github.com/ansible-community/ansible-build-data/milestones) for corresponding releases some time before releasing the package sufficient to solve all related issues. +## Blockers + +In the context of the Ansible Community package release workflow, a **release blocker** is a situation which does not allow the package to be released. +It might come with a new ``ansible-core`` release and affect many of the included collections or in any other way severe affect consistent work of the ``ansible`` package. +Severity of the impact is determined by the [Steering Committee](https://docs.ansible.com/ansible/devel/community/steering/community_steering_committee.html) in each particular case. +The release blocker must be resolved before the release can proceed. + +In case a release blocker, the following actions need to be done: + +* Create a [community topic](https://github.com/ansible-community/community-topics/issues) describing the potential blocker. +* If the [Steering Committee](https://docs.ansible.com/ansible/devel/community/steering/community_steering_committee.html) considers the circumstances a release blocker, create an [issue](https://github.com/ansible-community/ansible-build-data/issues/new) in this repository. +* Put the ``blocker`` label on the issue. +* Add the issue to a milestone for the [affected release](https://github.com/ansible-community/ansible-build-data/milestones). + ## Structure of data :: @@ -64,7 +80,7 @@ To add a collection to the next Ansible major release that has not reached featu directory). - `changelog-url` (string): If the collection does not provide a changelog in `changelogs/changelog.yaml`, the URL to the actual changelog needs to be - added. Otherwise, this field should be ommitted. + added. Otherwise, this field should be omitted. ``` yaml collections: From 29187cea4645ed9f8a799117dcfa6f915a8f088f Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Tue, 17 Jan 2023 08:46:43 +0100 Subject: [PATCH 2/4] Update README.md Co-authored-by: Mario Lenz --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8704a94645..3196208df1 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,7 @@ It might come with a new ``ansible-core`` release and affect many of the include Severity of the impact is determined by the [Steering Committee](https://docs.ansible.com/ansible/devel/community/steering/community_steering_committee.html) in each particular case. The release blocker must be resolved before the release can proceed. -In case a release blocker, the following actions need to be done: +In case of a potential release blocker, the following actions need to be done: * Create a [community topic](https://github.com/ansible-community/community-topics/issues) describing the potential blocker. * If the [Steering Committee](https://docs.ansible.com/ansible/devel/community/steering/community_steering_committee.html) considers the circumstances a release blocker, create an [issue](https://github.com/ansible-community/ansible-build-data/issues/new) in this repository. From 411c2c1addb60659e85258e4a7e96ee4993c1264 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Wed, 18 Jan 2023 09:06:26 +0100 Subject: [PATCH 3/4] Update README.md Co-authored-by: Mario Lenz --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3196208df1..91c0b7e5c1 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ Release engineers check the [milestones](https://github.com/ansible-community/an ## Blockers In the context of the Ansible Community package release workflow, a **release blocker** is a situation which does not allow the package to be released. -It might come with a new ``ansible-core`` release and affect many of the included collections or in any other way severe affect consistent work of the ``ansible`` package. +It might come with a new ``ansible-core`` release and affect many of the included collections or in any other way severely affects consistent work with the ``ansible`` package. Severity of the impact is determined by the [Steering Committee](https://docs.ansible.com/ansible/devel/community/steering/community_steering_committee.html) in each particular case. The release blocker must be resolved before the release can proceed. From feca84fca89f5b59f5010f34f245275cb7e8c955 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Wed, 18 Jan 2023 09:10:47 +0100 Subject: [PATCH 4/4] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 91c0b7e5c1..c5acdd3fb6 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ Release engineers check the [milestones](https://github.com/ansible-community/an ## Blockers In the context of the Ansible Community package release workflow, a **release blocker** is a situation which does not allow the package to be released. -It might come with a new ``ansible-core`` release and affect many of the included collections or in any other way severely affects consistent work with the ``ansible`` package. +It might come with a new ``ansible-core`` release and affect many of the included collections or in any other way might severely affect consistent work with the ``ansible`` package. Severity of the impact is determined by the [Steering Committee](https://docs.ansible.com/ansible/devel/community/steering/community_steering_committee.html) in each particular case. The release blocker must be resolved before the release can proceed.