Let’s discuss this here in the forum.
makes sense. probably makes sense to make the “new version” as small a bump as possible since nothing would be changing (unless the latest changes hadn’t yet been published to a release)
I think this is generally a good idea, but only in the right circumstances. The PR adds the text to the general “removal process” section, which might also be used when a still maintained collection is removed for other reasons.
I would probably adjust the text to make clear that these steps should only be followed in case the collection is removed because it is unmaintained.
(If you’re wondering about other scenarios: since we’re discussing potentially reducing the Ansible package size, we might also want to remove collections for other reasons - like thinking they are not useful for the majority of users - in the future.)
2 Likes
I’ve removed the community-wg-nextmtg since the repo has been archived. Maybe we should even close this thread, but I didn’t find out how to do it. Either I’m lacking permissions, or I’m too stupid.
Anyway, the important thing is to remove the community-wg-nextmtg tag.
@samccann If you think there’s still something we should work on, please let me know.