You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 14, 2024. It is now read-only.
The current process to identify and remove an unmaintained collection looks very much focused on abandoned collections. It takes quite long because we want to make sure that it is really not maintained anymore.
That's OK, but I think we should have a way to remove a collection that announces itself as being unmaintained / deprecated quicker. My suggestion is to remove a collection that announces itself as unmaintained or deprecated without a vote from the next major release.
I would like to clarify what 'next major Ansible version' means exactly. Because if feature freeze for the next one is tomorrow (as an extreme example), I think this should be delayed to the next one. How about: if Ansible X.4.0 has not yet been released, remove from (X+1).0.0. Otherwise, remove from (X+2).0.0. The X.4.0 release is approximately half-way between the X.0.0 and the (X+1).0.0 release.
(we shortened the period between feature freeze and GA, that's why the 6.4.0 release is closer to 7.0.0 than 6.0.0; in future cycles, this should be closer to the middle)
I would like to clarify what 'next major Ansible version' means exactly. Because if feature freeze for the next one is tomorrow (as an extreme example), I think this should be delayed to the next one.
Good point 👍
However, I think we shouldn't wait until X+2 if we're already on X.5.0. If the collection is deprecated, we should get rid of it as fast as possible.
I think there's one version where downwards incompatibility / breaking changes are problematic... RC1? I'm not sure. But I think it would be OK to remove an officially unmaintained collection up until then.
Summary
This is a follow-up to #124
The current process to identify and remove an unmaintained collection looks very much focused on abandoned collections. It takes quite long because we want to make sure that it is really not maintained anymore.
That's OK, but I think we should have a way to remove a collection that announces itself as being unmaintained / deprecated quicker. My suggestion is to remove a collection that announces itself as unmaintained or deprecated without a vote from the next major release.
Suggestion: ansible-collections/overview#214
The text was updated successfully, but these errors were encountered: