Open Stack

As discussed previously on IRC, my understanding of the official policy as it stands now[1] is:

"OpenStack will target its development efforts to latest Ubuntu/Fedora, but will endeavor to not introduce any changes that would make it impossibly or unnaturally difficult to run on the latest Ubuntu LTS or latest RHEL."


Keeping the fact that Ubuntu LTS will no longer support Python 2.x as of 2014.4,  the current policy could be interpreted as an ultimatum to have dual-version support by the time the next LTS lands, or at least not to create new projects that cannot work on Python3.

--
Eric Windisch


[1] Per the following email from Monty which was subsequently taken to vote and ratified:
http://lists.openstack.org/pipermail/openstack-dev/2012-December/004052.html


On June 12, 2013 at 13:00:12 , Joe Gordon (joe.gordon0 at gmail.com) wrote:



On Wed, Jun 12, 2013 at 4:31 AM, Thierry Carrez <thierry at openstack.org> wrote:
Julien Danjou wrote:
> On Tue, Jun 11 2013, Joe Gordon wrote:
>> As many of you have probably seen, there has been a community
>> effort to begin the slow process to making OpenStack python 3
>> compatible. There is even a weekly meeting discussion it (
>> http://eavesdrop.openstack.org/meetings/python3/2013/)
>>
>> As this is inherently a massive cross project effort, I was
>> hoping the TC would comment on the python 3 efforts.
>>
>> * What versions of python we want to compatible with * Do we
>> *want* all projects to by python 3 compatible or should we focus
>> our efforts on oslo and client libraries etc? * Do we want to
>> begin gating on some python 3 compatibility?
>> https://github.com/openstack-dev/hacking/commit/e0ab03637da65bfc6035091989b62fc70ae363a5
>>
>>
>
> It kind of seems obvious to me that nobody in the TC is going to
> object to any effort bringing compatibility to Python 3. :-) I
> bless that and would love to help going into this direction
> actually.

Yeah, I don't really think you need the TC involved at this point...
discussion on -dev and lazy consensus should work perfectly alright.
If you end up facing opposition and we end up needing to pick between
going Py3 and not going Py3, I guess that would warrant a TC
discussion, but I don't expect we'll ever come to that. The few times
it was mentioned in the past there was unanimous support for it...
just not enough resources to drive it.

Thank you all for the feedback, this addressed my underlying question, is there consensus on py3 before we start adding several hacking checks for it in hacking 0.6.
 

Happy to see the effort getting more momentum!

--
Thierry Carrez (ttx)

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130612/68d86891/attachment.html>