Open Stack

This is exactly what I did in [1].

Cheers,
Armando

[1]
https://review.openstack.org/#/q/status:open+branch:master+topic:neutron-unstable,n,z

On 12 June 2015 at 09:00, Clint Byrum <clint at fewbar.com> wrote:

> Excerpts from Chris Dent's message of 2015-06-12 03:47:02 -0700:
> > On Fri, 12 Jun 2015, Joe Gordon wrote:
> >
> > > Glad to see us catch these issues early.
> >
> > Yes! CI is doing exactly the job it is supposed to be doing here. It
> > is finding bugs in code. When that happens we should fix the bugs,
> > not revert. Even if it stalls other stuff.
> >
>
> I'd like to offer an alternative path. Please do remember that people
> deploy OpenStack from trunk, and we want them to do that, because if an
> organization is focused and prepared, continuous deployment will produce
> a vibrant OpenStack experience for users, and will keep those operators
> in a position to contribute.
>
> We also have hundreds of developers who need the system to work well.
> There are maybe only a handful who will work on this issue. It does not
> make any sense to me to stall hundreds of developers while a handful
> work through something that may take weeks.
>
> So, consider reverting _quickly_, landing a test that fails at least more
> reliably with the current patch, and then have that handful of users who
> are capable of fixing it work in their own branch until the problem is
> resolved to a level that it won't stand in the way of progress for CD
> operators and the development community at large.
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> 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/20150612/20641bc5/attachment.html>