Mario Lenz

> I guess we can still un-deprecate it if we're happy with the result (and the explanation why it took so long). But how would we document this in the...

Thanks @dmsimard, great work! I'm having a look at the output for `community.vmware`. `vca_fw` and `vca_nat` fail the tests: ``` ERROR: Found 2 validate-modules issue(s) which need to be resolved:...

> you don't see these errors in Zuul since you don't test against stable-2.13. You only test against devel (and the errors are correctly ignored in the ignore-2.14.txt), but then...

> you test against milestone, which is a very out of date version of stable-2.13. It basically is the state of the devel branch on 2022-02-14. Shouldn't the milestone branch...

> I've ran a comprehensive sanity test on every collection included in 6.0.0a2 (minus pylint) and found that 67 collections (out of 98) are currently failing sanity tests Maybe some...

> Sanity tests can be actually fixed like in [ansible-collections/community.rabbitmq#121](https://github.com/ansible-collections/community.rabbitmq/issues/121) but not released yet. > > * The question is if they should appear on Galaxy and there's nothing else...

@dmsimard The `community.dns` issue is already closed, and I don't see that you've opened one in `community.general`. So it looks like these issues are left to be closed since the...

@dmsimard I can't close those issues due to missing permissions :-/ But I've added a comment that they can be closed because of a false positive from our side.

@dmsimard Most of the issues in the collections that don't fail any more have been closed already. I have added a comment that the tests seem to succeed in 6.0.0a3...

@felixfontein Please close this issue if done, or open a new forum topic and then close the issue with a pointer to the new discussion: [Community-topics: Archiving the repo](https://forum.ansible.com/t/4990/8)