Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add release blocker WF #194

Merged
merged 4 commits into from
Jan 18, 2023
Merged

Add release blocker WF #194

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d6568dc
Add release blocker WF
Andersson007 Jan 12, 2023
29187ce
Update README.md
Andersson007 Jan 17, 2023
411c2c1
Update README.md
Andersson007 Jan 18, 2023
feca84f
Update README.md
Andersson007 Jan 18, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 17 additions & 1 deletion README.md
View file
Open in desktop
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 severe affect consistent work of the ``ansible`` package.
Andersson007 marked this conversation as resolved.
Show resolved Hide resolved
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