On Mon, Aug 27, 2018 at 2:37 PM Doug Hellmann <d...@doughellmann.com> wrote:
> This is week 3 of the "Run under Python 3 by default" goal > (https://governance.openstack.org/tc/goals/stein/python3-first.html). > > == What we learned last week == > > We have a few enthusiastic folks who want to contribute to the goal > who have not been involved in the previous discussion with goal > champions. If you are one of them, please get in touch with me > BEFORE beginning any work. > http://lists.openstack.org/pipermail/openstack-dev/2018-August/133610.html > > In the course of adding python 3.6 unit tests to Manilla, a recursion > bug setting up the SSL context was reported. > https://bugs.launchpad.net/manila/+bug/1788253 (We could use some > help debugging it.) > > Several projects have their .gitignore files set up to ignore all > '.' files. I'm not sure why this is the case. It has caused some > issues with the migration, but I think we've worked around the > problem in the scripts now. > > We extended the scripts for generating the migration patches to > handle the neutron-specific versions of the unit test jobs for > python 3.5 and 3.6. > > The Storyboard UI has some performance issue when a single story > has several hundred comments. This is an unusual situation, which > we don't expect to come up for "normal" stories, but the SB team > discussed some ways to address it. > > Akihiro Mitoki expressed some concern about the new release notes > job being set up in horizon, and how to test it. The "new" job is > the same as the "old" job except that it sets up sphinx using > python3. The versions of sphinx and reno that we rely on for the > release notes jobs all work under python3, and projects don't have > any convenient way to install extra dependencies, so we are confident > that the new version of the job works. If you find that not to be > true for your project, we can help fix the problem. > > We have a few repos with unstable functional tests, and we seem to > have some instability in the integrated gate as well. > > == Ongoing and Completed Work == > > These teams have started or completed their Zuul migration work: > > +---------------------+------+-------+------+ > | Team | Open | Total | Done | > +---------------------+------+-------+------+ > | Documentation | 0 | 12 | yes | > | OpenStack-Helm | 5 | 5 | | > | OpenStackAnsible | 70 | 270 | | > | OpenStackClient | 10 | 19 | | > | OpenStackSDK | 12 | 15 | | > | PowerVMStackers | 0 | 15 | yes | > | Technical Committee | 0 | 5 | yes | > | blazar | 16 | 16 | | > | congress | 1 | 16 | | > | cyborg | 2 | 9 | | > | designate | 10 | 17 | | > | ec2-api | 4 | 7 | | > | freezer | 26 | 30 | | > | glance | 16 | 16 | | > | horizon | 0 | 8 | yes | > | ironic | 22 | 60 | | > | karbor | 30 | 30 | | > | keystone | 35 | 35 | | > | kolla | 1 | 8 | | > | kuryr | 26 | 29 | | > | magnum | 24 | 29 | | > | manila | 19 | 19 | | > | masakari | 18 | 18 | | > | mistral | 0 | 25 | yes | > | monasca | 20 | 69 | | > | murano | 25 | 25 | | > | octavia | 5 | 23 | | > | oslo | 3 | 157 | | > | other | 3 | 7 | | > | qinling | 1 | 6 | | > | requirements | 0 | 5 | yes | > | sahara | 0 | 27 | yes | > | searchlight | 5 | 13 | | > | solum | 0 | 17 | yes | > | storlets | 5 | 5 | | > | swift | 9 | 11 | | > | tacker | 16 | 16 | | > | tricircle | 5 | 9 | | > | tripleo | 67 | 78 | | > | vitrage | 0 | 17 | yes | > | watcher | 12 | 17 | | > | winstackers | 6 | 11 | | > | zaqar | 12 | 17 | | > | zun | 0 | 13 | yes | > +---------------------+------+-------+------+ > > == Next Steps == > > If your team is ready to have your zuul settings migrated, please > let us know by following up to this email. We will start with the > volunteers, and then work our way through the other teams. > > The keystone team is ready. Just FYI - there are pre-existing patches proposed to our repositories, but they weren't initiated by one of the goal champions [0]. I can help work through issues on our end. [0] https://review.openstack.org/#/q/(status:open+OR+status:merged)+project:openstack/keystone+topic:python3-first > After the Rocky cycle-trailing projects are released, I will propose > the change to project-config to change all of the packaging jobs > to use the new publish-to-pypi-python3 template. We should be able > to have that change in place before the first milestone for Stein > so that we have an opportunity to test it. > > == How can you help? == > > 1. Choose a patch that has failing tests and help fix it. > > https://review.openstack.org/#/q/topic:python3-first+status:open+(+label:Verified-1+OR+label:Verified-2+) > 2. Review the patches for the zuul changes. Keep in mind that some of > those patches will be on the stable branches for projects. > 3. Work on adding functional test jobs that run under Python 3. > > == How can you ask for help? == > > If you have any questions, please post them here to the openstack-dev > list with the topic tag [python3] in the subject line. Posting > questions to the mailing list will give the widest audience the > chance to see the answers. > > We are using the #openstack-dev IRC channel for discussion as well, > but I'm not sure how good our timezone coverage is so it's probably > better to use the mailing list. > > == Reference Material == > > Goal description: > https://governance.openstack.org/tc/goals/stein/python3-first.html > Open patches needing reviews: > https://review.openstack.org/#/q/topic:python3-first+is:open > Storyboard: https://storyboard.openstack.org/#!/board/104 > Zuul migration notes: https://etherpad.openstack.org/p/python3-first > Zuul migration tracking: https://storyboard.openstack.org/#!/story/2002586 > Python 3 Wiki page: https://wiki.openstack.org/wiki/Python3 > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev