[openstack-dev] Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))
anteaya at anteaya.info
Mon Mar 23 20:23:44 UTC 2015
On 03/23/2015 03:59 PM, Stefano Maffulli wrote:
> On Mon, 2015-03-23 at 11:43 -0700, Mike Perez wrote:
>> We've been talking about CI's for a year. We started talking about CI deadlines
>> in August. If you post a driver for Kilo, it was communicated that you're
>> required to have a CI by the end of Kilo . This
>> should've been known by your engineers regardless of when you submitted your
> Let's work to fix the CI bits for Liberty and beyond. I have the feeling
> that despite your best effort to communicate deadlines, some quite
> visible failure has happened.
The thing that quite visibly that happened is that some folks don't
recognize that their actions affect others and take responsibility for
those actions. I have learned much to my dismay that there is a certain
percentage of a group that will not follow the intent of the group
despite any amount of support given to them.
> You've been clear about Cinder's deadlines, I've been trying to add them
> also to the weekly newsletter, too.
> To the people whose drivers don't have their CI completed in time: what
> do you suggest should change so that you won't miss the deadlines in the
Asking this question dismisses all the hard work that both Mike and
myself and many others including some very committed operators have put
into this space.
Some folks just will not respect other people's time. To pretend
otherwise is a huge dis-service to folks trying their hardest to support
those worthy of the support.
I'm really disappointed that there hasn't been more support for Mike in
this process. I can see how everyone thought I was the problem last year
when I had to endure this kind of treatment in Neutron, but I would
think after seeing the exact same kind of behaviour a second time folks
might be starting to see the pattern.
> How should the processes and tool be different so you'll be
> successful with your OpenStack-based products?
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev