[infra][neutron] Removing networking-calico from OpenStack governance

Neil Jerram neil at tigera.io
Tue Feb 11 19:43:38 UTC 2020

On Tue, Feb 11, 2020 at 7:37 PM Jeremy Stanley <fungi at yuggoth.org> wrote:

> On 2020-02-11 19:31:28 +0000 (+0000), Neil Jerram wrote:
> > Thanks for this question.  I think the answer is that it will be a
> planned
> > effort, from now on, for us to support new OpenStack versions.  From Kilo
> > through to Rocky we have aimed (and managed, so far as I know) to
> maintain
> > a unified networking-calico codebase that works with all of those
> > versions.  However our code does not support Python 3, and OpenStack
> master
> > now requires Python 3, so we have to invest work in order to have even
> the
> > possibility of working with Train and later.
> [...]
> It's probably known to all involved in the conversation here, but
> just for clarity, the two releases immediately following Rocky (that
> is, Stein and Train) are still supposed to support Python 2.7. Only
> as of the Ussuri release (due out in a few more months) will
> OpenStack be Python3-only.

Sorry; thanks for this correction.  (So I should have said "... even the
possibility of working with Ussuri and later.")

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200211/588bc90c/attachment.html>

More information about the openstack-discuss mailing list