[openstack-dev] [all] Status of the OpenStack port to Python 3
tony at bakeyournoodle.com
Thu Jun 23 08:59:52 UTC 2016
On Thu, Jun 23, 2016 at 10:08:22AM +0200, Sylvain Bauza wrote:
> Le 23/06/2016 02:42, Tony Breeds a écrit :
> > On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote:
> > > Le 22/06/2016 à 10:49, Thomas Goirand a écrit :
> > > > Do you think it looks like possible to have Nova ported to Py3 during
> > > > the Newton cycle?
> > > It doesn't depend on me: I'm sending patches, and then I have to wait for
> > > reviews. The question is more how to accelerate reviews.
> > Clearly I'm far from authorative but given how close we are to R-14 which is
> > the Nova non-priority feature freeze and the python3 port isn't listed as
> > a priority I'd guess that this wont land in Newton.
> >  http://releases.openstack.org/newton/schedule.html#nova-non-priority-feature-freeze
> >  http://specs.openstack.org/openstack/nova-specs/priorities/newton-priorities.html
> Well, IIRC we discussed in the previous year on some of those blueprints
> (including the Py3 effort) that are not really features (rather refactoring
> items) and which shouldn't be hit by the non-priority feature freeze.
> That doesn't mean we could merge those anytime of course, but I don't think
> we would procedurally -2 them.
Sure I didn't mean to imply a proceedural -2 I meant to convey that at this
point in the cycle review focus shifts to priority items. So getting attention
for this effort will be hard.
We did discuss that this (py3 support) was a great background task but we also
noted that those tasks would have a cut-off point. I *thought* that was the
Nova non-priority feature freeze but I can't find that written anywhere.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 473 bytes
Desc: not available
More information about the OpenStack-dev