Hi all-
For all those wanting to test the next version of Ansible, we're happy
to announce that Ansible 2.10.0 beta1 is now available on PyPI!
Ansible 2.10.0b1 pulls in the ansible-base-2.10.1 (presently rc2)
package via a dependency and includes a range of Ansible Collections.
The Ansible 2.10 PyPI packages provide similar functionality to
Ansible 2.9 and earlier versions, but from multiple sources. The
included Ansible Collections are maintained by a host of open source
contributors who want to add to what ansible-base has to offer.
For an overview of "Ansible Collections" and the differences between
`ansible-base` and `ansible` please see
https://github.com/ansible-collections/overview/blob/master/README.rst
We need your help
Howdy folks!
We're entering the final weeks of the Ansible 2.10.0 release cycle and
I wanted to let anyone testing the Ansible betas and release candidate
on how to nominate a bug as a release blocker.
* If you find something major enough to block the Ansible release,
please add a comment on the Community Meeting Agenda:
https://github.com/ansible/community/issues/539 asking us to consider
whether the issue is a blocker. If the issue has a ticket open
elsewhere, linking to the ticket will be appreciated.
* If at all possible, attend the IRC meeting on Thursday, September
17th, 2020, 18:00 UTC to state your case as to why the issue should
block the release.
* We'll decide at the meeting whether to slip the Ansible-2.10.0 final
release for any of the listed blockers.
*Important*: If the Meeting Agenda does not contain any comments
listing potential blockers when the meeting starts on Thursday, we'll
end the meeting early. We will wait for five minutes or so to see if
anyone proposes a blocker at the start of the meeting itself but
otherwise we'll cut the meeting short. So please, if you have a
candidate blocker; get your issue listed on the Community Agenda ASAP.
What should you do if you notice a blocker after the meeting time?
You can still report it on the Community Meeting Agenda. However,
it's likely that only myself and a few other people will be able to
look at and evaluate it before the release date and we'll likely
lean towards fixing anything that wasn't noticed previously in the
Ansible-2.10.1 release. So please test out the beta and release
candidate now and report candidate blockers before the meeting.
Thank you,
Toshio Kuratomi
One more piece of information: The meeting on the 17th of September
will take place in the #ansible-community channel on irc.freenode.net.
Note that if you haven't used freenode before, you can use online
webchat to access freenode: https://webchat.freenode.net/
Because of issues with spam and harassment, you'll need to register to
participate in our channels:
https://freenode.net/kb/answer/registration I highly recommend
registering and testing that you are able to participate in
#ansible-community discussions before the meeting on the 17th!
-Toshio
And yes... apparently I suck at email :-(. Posting this to the
correct subthread in case anyone is following this conversation on the
google groups forum interface instead of via a threaded email client:
One more piece of information: The meeting on the 17th of September
will take place in the #ansible-community channel on irc.freenode.net.
Note that if you haven't used freenode before, you can use online
webchat to access freenode: https://webchat.freenode.net/
Because of issues with spam and harassment, you'll need to register to
participate in our channels:
https://freenode.net/kb/answer/registration I highly recommend
registering and testing that you are able to participate in
#ansible-community discussions before the meeting on the 17th!
-Toshio