<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">Le 23/06/2016 02:42, Tony Breeds a
écrit :<br>
</div>
<blockquote cite="mid:20160623004241.GM645@thor.bakeyournoodle.com"
type="cite">
<pre wrap="">On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Le 22/06/2016 à 10:49, Thomas Goirand a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">Do you think it looks like possible to have Nova ported to Py3 during
the Newton cycle?
</pre>
</blockquote>
<pre wrap="">
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.
</pre>
</blockquote>
<pre wrap="">
Clearly I'm far from authorative but given how close we are to R-14 which is
the Nova non-priority feature freeze[1] and the python3 port isn't listed as
a priority[2] I'd guess that this wont land in Newton.
[1] <a class="moz-txt-link-freetext" href="http://releases.openstack.org/newton/schedule.html#nova-non-priority-feature-freeze">http://releases.openstack.org/newton/schedule.html#nova-non-priority-feature-freeze</a>
[2] <a class="moz-txt-link-freetext" href="http://specs.openstack.org/openstack/nova-specs/priorities/newton-priorities.html">http://specs.openstack.org/openstack/nova-specs/priorities/newton-priorities.html</a>
</pre>
</blockquote>
<br>
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.<br>
That doesn't mean we could merge those anytime of course, but I
don't think we would procedurally -2 them.<br>
<br>
My .02€<br>
-Sylvain<br>
<br>
<blockquote cite="mid:20160623004241.GM645@thor.bakeyournoodle.com"
type="cite">
<pre wrap="">
Yours Tony.
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>