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 On Thu, Sep 10, 2020 at 8:29 AM Toshio Kuratomi <[email protected]> wrote: > > 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 > > On Tue, Sep 1, 2020 at 11:21 PM Toshio Kuratomi <[email protected]> wrote: > > > > 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 > > ----------------- > > > > This new `ansible` package *should* be a drop-in replacement for > > Ansible 2.9. The roles and playbooks that you currently use should > > work out of the box with ansible-2.10.0 beta1. > > > > Please let us know if: > > > > * Your playbooks don't work > > * There are any installation issues > > * Whether the collections are found OK > > * If the updated and new modules in the collections work > > > > How to get it > > ------------- > > > > Due to a limitation in pip, you need to uninstall Ansible 2.9 (or > > earlier) before installing the 2.10 version: > > > > $ pip uninstall ansible > > $ pip install ansible==2.10.0b1 --user > > > > The tar.gz of the release can be found here: > > > > * Ansible 2.10.0b1 > > https://pypi.python.org/packages/source/a/ansible/ansible-2.10.0b1.tar.gz > > SHA256: 081c1b1ea95a0b67f8bf1e5c3c45b8e8dd8bafd1f8d05838f96239da3496ce8f > > > > > > What's new in Ansible 2.10.0b1 > > ------------------------------ > > > > * Collections which have opted into being a part of the Ansible-2.10.0 > > unified changelog will have an entry on this page: > > https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst > > > > * For other collections, consult the list of included collections in > > the link below and check their entry on https://galaxy.ansible.com for > > information about their changes. > > > > * List of collections included in the 2.10.0b1 release: > > * > > https://github.com/ansible-community/ansible-build-data/blob/2.10.0b1/2.10/ansible-2.10.0b1.deps > > * You can find more information for those on > > https://galaxy.ansible.com/. For instance, the community.crypto > > collection listed in the ansible-2.10.0b1.deps file has a galaxy page > > here at https://galaxy.ansible.com/community/crypto/ > > > > * Changelog for ansible-base-2.10.1 which this release of ansible installs: > > > > https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst > > > > > > Caveats and known bugs > > ---------------------- > > > > * The individual collections that make up the ansible-2.10.0 package > > can be viewed independently. However, they aren't currently listed by > > ansible-galaxy. A workaround for this is to explicitly specify where > > ansible has installed the collections:: > > > > COLLECTION_INSTALL=$(python -c 'import ansible, os.path ; > > print("%s/../ansible_collections" % > > os.path.dirname(ansible.__file__))') ansible-galaxy collection list -p > > "$COLLECTION_INSTALL" > > > > * A fix has been proposed but was not be merged for 2.10.0. This is > > being tracked in this bug report: > > https://github.com/ansible/ansible/issues/70147 > > > > * Due to a limitation in pip, you cannot `pip install --upgrade` from > > ansible-2.9 or earlier to ansible-2.10 or higher. Instead, you must > > explicitly `pip uninstall ansible` before pip installing the new > > version. The install of the ansible package has been modified to warn > > you if you attempt to upgrade via pip with instructions to uninstall > > first. > > > > > > What's the schedule for the rest of the 2.10.0 release cycle? > > ------------------------------------------------------------- > > > > ansible-2.10.0rc1 is due to be released on 2020-09-10 > > ansible-2.10.0 final is due out on 2020-09-22 > > > > The ansible-2.10 roadmap reflects these dates: > > https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_2_10.html > > > > Porting Help > > ------------ > > > > There's a unified porting guide for collections which have opted-in. > > You can find that at: > > https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst > > > > If you encounter any bugs, please report them. We're putting together > > a draft document which includes where to report bugs on various parts > > of the ansible package: > > * > > https://github.com/ansible/community/wiki/User-testing-of-ansible-2.10-pre-releases > > > > If you aren't sure where your bug falls, pick which you feel is > > closest and the Community Team will always move it if needed > > > > Thanks! > > > > -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAPrnkaTv%2BPPXXUD845u6thP5yp%2BL162YeDnHn8T%3D0Xzg7dDURA%40mail.gmail.com.
