-
Notifications
You must be signed in to change notification settings - Fork 9
[associated vote ended on 2022-11-08] Collection Removal Policy: add a paragraph about Collection Requirements violations #150
Comments
+1 - I think having advertised clarity here will be beneficial |
Noticed that I didn't put the vote discussion link here Thanks:) |
I've counted the vote:
Could anyone please confirm the count? |
I've counted the same numbers. |
closed via ansible-collections/overview#217, thanks everyone! |
How should we handle non-compliant collection that we already filed issues against (e.g. the collections that don't tag releases, the ones with failing sanity tests)? Would it make sense to go through those issues and leave comments saying that collections which don't fix the violations in four weeks from now will be subject to removal? |
IMO we should |
Summary
It was discussed in the community meeting that we should explicitly include Collection Requirements violations as a reason to remove collections from the package.
Relates to #148
I created a PR ansible-collections/overview#217 to discuss, polish, merge/reject. Please take a look and comment.
The text was updated successfully, but these errors were encountered: