Network/Lib/Meetings

Meeting time: The neutron-lib sub-Team (Neutron-Lib) holds public meetings on Wednesdays at 1730 UTC in the #openstack-meeting-4 channel on Freednode. Everyone is encouraged to attend.

Announcements / Reminders

None this week

Current Work Items

Using the lib in neutron - https://review.openstack.org/#/c/268232/
Moving base db gunk - https://review.openstack.org/#/c/267214/

Open Discussion

[boden]

Looking for feedback on the high-level approach for a public python API generation tool as in 338571. NB: code is not ready for review, just looking to understand if the current approach is worth honing further.
Have we put any thought into what impacts it would have if we released neutron-lib more frequently/continuously? For example suppose we did releases of neutron-lib every 2 weeks (for sake of argument); what implications would that have to our process and consumers? With our current release process there's a large latency when trying to get function into lib. While I understand the merits of this approach, it "seems" to impact adoption/consumption.
As per our meeting I thought we were going to get the neutron pep8 jobs running for neutron-lib gate? Is that going to happen?