Corey Bryant <> writes:

> On Wed, Oct 10, 2018 at 8:45 AM Corey Bryant <>
> wrote:
> I'd like to start moving forward with enabling py37 unit tests for a subset
> of projects. Rather than putting too much load on infra by enabling 3 x py3
> unit tests for every project, this would just focus on enablement of py37
> unit tests for a subset of projects in the Stein cycle. And just to be
> clear, I would not be disabling any unit tests (such as py35). I'd just be
> enabling py37 unit tests.
> As some background, this ML thread originally led to updating the
> python3-first governance goal (
> but has now led back to this ML thread for a +1 rather than updating the
> governance goal.
> I'd like to get an official +1 here on the ML from parties such as the TC
> and infra in particular but anyone else's input would be welcomed too.
> Obviously individual projects would have the right to reject proposed
> changes that enable py37 unit tests. Hopefully they wouldn't, of course,
> but they could individually vote that way.
> Thanks,
> Corey

This seems like a good way to start. It lets us make incremental
progress while we take the time to think about the python version
management question more broadly. We can come back to the other projects
to add 3.7 jobs and remove 3.5 jobs when we have that plan worked out.


OpenStack Development Mailing List (not for usage questions)

Reply via email to