Skip to content

Commit

Permalink
Add release blocker WF (#194)
Browse files Browse the repository at this point in the history
* Add release blocker WF

* Update README.md

Co-authored-by: Mario Lenz <m@riolenz.de>

* Update README.md

Co-authored-by: Mario Lenz <m@riolenz.de>

* Update README.md

Co-authored-by: Mario Lenz <m@riolenz.de>
  • Loading branch information
Andersson007 and mariolenz authored Jan 18, 2023
1 parent 71cd081 commit 7c82cdd
Showing 1 changed file with 17 additions and 1 deletion.
18 changes: 17 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 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.

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.
* 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

::
Expand Down Expand Up @@ -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:
Expand Down

0 comments on commit 7c82cdd

Please sign in to comment.