Release 2.0 - change to an ansible collection

[aalaesar]

Preparing release
@staticdev can the release drafter manage all the changes here or should we edit it ? I noted that is has overwritten my comments on the draft release last time.

[staticdev]

Preparing release @staticdev can the release drafter manage all the changes here or should we edit it ? I noted that is has overwritten my comments on the draft release last time.

Release Drafter considers all PRs to main, except with tag skip-changelog as one change. In this case, makes sense to edit manually since it is a special case.

[aalaesar]

Preparing release @staticdev can the release drafter manage all the changes here or should we edit it ? I noted that is has overwritten my comments on the draft release last time.

Release Drafter considers all PRs to main, except with tag skip-changelog as one change. In this case, makes sense to edit manually since it is a special case.

Ok but I have a doubt : last time I edited the release draft to add a comment that this was the last release as a role, but this comment is not in the 1.8.0 release.
unless someone removed it ?

[aalaesar]

I expect troubles with galaxy when this PR is merged.

I haven't found doc about converting a role into a collection for galaxy (and keeping stats)
could be a nice exp for when transferring to nextcloud (but it will have a larger exposure so good stats may not be that hard to get)

I didn't found doc about transferring a role in galaxy to an other organization either...

[staticdev]

I expect troubles with galaxy when this PR is merged.

I haven't found doc about converting a role into a collection for galaxy (and keeping stats) could be a nice exp for when transferring to nextcloud (but it will have a larger exposure so good stats may not be that hard to get)

I didn't found doc about transferring a role in galaxy to an other organization either...

@aalaesar I also had the same problem. Probably there was a merge of PR after your edit and then Release-Drafter overwritten it. This is why currently I edit after the release to be 100% safe =p

Also, regarding problems when this PR is merged, I also expect. The sooner we do it, the better. We can make PR fixes as we go, when we have a change like that is 99.99% chance something will break. It is ok if we accept that and keep fixing.

[wiktor2200]

I've taken a look on whole PR. I was able to verify all file moves, yml and other. I've not verified python plugins (I think nothing has changed since last review by @staticdev).

[staticdev]

@aalaesar I think you will need somehow to rebase to be able to merge since Github says there is a conflict in meta/main.yml

[staticdev]

Lets go.

[wiktor2200]

LGTM :)