Open Stack

Excerpts from Emilien Macchi's message of 2017-06-01 15:31:10 +0200:
> On Wed, May 31, 2017 at 10:38 PM, Mike <thingee at gmail.com> wrote:
> > Hello everyone,
> >
> > For this thread we will be discussing continuing Python 3.5+ support.
> > Emilien who has been helping with coordinating our efforts here with
> > Pike can probably add more here, but glancing at our goals document
> > [1] it looks like we have a lot of unanswered projects’ status, but
> > mostly we have python 3.5 unit test voting jobs done thanks to this
> > effort! I have no idea how to use the graphite dashboard, but here’s a
> > graph [2] showing success vs failure with python-35 jobs across all
> > projects.
> 
> Indeed, nice work from the community to make progress on this effort.
> 
> > Glancing at that I think it’s safe to say we can start discussions on
> > moving forward with having our functional tests support python 3.5.
> > Some projects are already ahead in this. Let the discussions begin so
> > we can aid the decision in the  TC deciding our community wide goals
> > for Queens [3].
> 
> +1 - making progress on functional tests looks like the next thing and
> Queens cycle could be used. I'm happy to keep helping on coordination
> if needed.

Unit tests were optional, according to the goal. The functional and
integration tests are much more important.

I know we have the integrated gate running on python 3, so that
covers cinder, glance, keystone, neutron, nova, as well as devstack
and tempest. How are other projects doing with getting their similar
jobs set up and running?

Doug

> 
> >
> > [1] - https://governance.openstack.org/tc/goals/pike/python35.html
> > [2] - http://graphite.openstack.org/render/?width=1273&height=554&_salt=1496261911.56&from=00%3A00_20170401&until=23%3A59_20170531&target=sumSeries(stats.zuul.pipeline.gate.job.gate-*-python35.SUCCESS)&target=sumSeries(stats.zuul.pipeline.gate.job.gate-*-python35.FAILURE)
> > [3] - https://governance.openstack.org/tc/goals/index.html
> >
> > —
> > Mike Perez
>