[openstack-dev] [infra] [neutron] [tc] Neutron Incubator workflow

Kevin Benton blak111 at gmail.com
Wed Aug 27 20:28:31 UTC 2014

What are you talking about? The only reply was from me clarifying that one
of the purposes of the incubator was for components of neutron that are
experimental but are intended to be merged. In that case it might not make
sense to have a life cycle of their own in another repo indefinitely.

On Wed, Aug 27, 2014 at 11:52 AM, Jay Pipes <jaypipes at gmail.com> wrote:

> On 08/26/2014 07:09 PM, James E. Blair wrote:
>> Hi,
>> After reading https://wiki.openstack.org/wiki/Network/Incubator I have
>> some thoughts about the proposed workflow.
>> We have quite a bit of experience and some good tools around splitting
>> code out of projects and into new projects.  But we don't generally do a
>> lot of importing code into projects.  We've done this once, to my
>> recollection, in a way that preserved history, and that was with the
>> switch to keystone-lite.
>> It wasn't easy; it's major git surgery and would require significant
>> infra-team involvement any time we wanted to do it.
>> However, reading the proposal, it occurred to me that it's pretty clear
>> that we expect these tools to be able to operate outside of the Neutron
>> project itself, to even be releasable on their own.  Why not just stick
>> with that?  In other words, the goal of this process should be to create
>> separate projects with their own development lifecycle that will
>> continue indefinitely, rather than expecting the code itself to merge
>> into the neutron repo.
>> This has advantages in simplifying workflow and making it more
>> consistent.  Plus it builds on known integration mechanisms like APIs
>> and python project versions.
>> But more importantly, it helps scale the neutron project itself.  I
>> think that a focused neutron core upon which projects like these can
>> build on in a reliable fashion would be ideal.
> Despite replies to you saying that certain branches of Neutron development
> work are special unicorns, I wanted to say I *fully* support your above
> statement.
> Best,
> -jay
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Kevin Benton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140827/677f792b/attachment.html>

More information about the OpenStack-dev mailing list