Mike,
This effort has taken quite some time and was going to require hard
decisions to be made at some point. You have been more than patient in
this process and I commend you for that as well as all the communication.
Thank you for continuing to drive this!
Jay
On Mar 24, 2015 10:55 PM,
On Tue, Mar 24, 2015 at 4:52 AM, Thierry Carrez thie...@openstack.org
wrote:
Walter A. Boring IV wrote:
Thanks Mike for all of your efforts on this,
+1
I think Mike checked all the possible boxes to give fair warning to
driver owners.
It's hard to say no in the name of quality. It's so
On Mar 24, 2015, at 9:30 AM, John Griffith john.griffi...@gmail.com wrote:
On Tue, Mar 24, 2015 at 4:52 AM, Thierry Carrez thie...@openstack.org
mailto:thie...@openstack.org wrote:
Walter A. Boring IV wrote:
Thanks Mike for all of your efforts on this,
+1
I think Mike checked
Walter A. Boring IV wrote:
Thanks Mike for all of your efforts on this,
+1
I think Mike checked all the possible boxes to give fair warning to
driver owners.
It's hard to say no in the name of quality. It's so much easier to
just say yes and avoid all the hatemail and the pressure.
Mike did
On Tue, Mar 24, 2015 at 2:51 AM, Walter A. Boring IV walter.bor...@hp.com
wrote:
On 03/23/2015 01:50 PM, Mike Perez wrote:
On 12:59 Mon 23 Mar , 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
I also absolutely agree that Mike did a great job on the communication
with the driver maintainers and a lot more, especially in the hectic days
around the K-3 deadline.
Removing any driver lacking CI testing was just the right thing to do, even if
this affected our SMB3 driver. Hopefully this is
On Tue, Mar 24, 2015 at 9:56 AM, Doug Hellmann d...@doughellmann.com
wrote:
Excerpts from Mark McClain's message of 2015-03-24 10:25:31 -0400:
Echoing both Thierry and John. I support Mike’s decision to enforce the
requirement. Maintaining drivers in the tree comes with responsibilities to
+10 to mike; I have no doubt this is an uneasy and tough task.
Thanks mike for pushing this through; given all the challenges and hard
work (and likely not fun work) that had to be done.
I salute u! :)
-Josh
Duncan Thomas wrote:
On 23 March 2015 at 22:50, Mike Perez thin...@gmail.com
On 03/24/2015 06:05 PM, Kyle Mestery wrote:
On Tue, Mar 24, 2015 at 9:56 AM, Doug Hellmann d...@doughellmann.com
wrote:
Excerpts from Mark McClain's message of 2015-03-24 10:25:31 -0400:
Echoing both Thierry and John. I support Mike’s decision to enforce the
requirement. Maintaining
List (not for usage questions)
Subject: Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re:
[cinder] Request exemption for removal of NetApp FC drivers (no voting CI))
I’d like to suggest that the myriad wiki pages and spreadsheets for Third Party
CI also be consolidated to a more
Excerpts from Mark McClain's message of 2015-03-24 10:25:31 -0400:
Echoing both Thierry and John. I support Mike’s decision to enforce the
requirement. Maintaining drivers in the tree comes with responsibilities to
the community and 3rd party CI is one of the them. Mike enforcing this
On Mon, Mar 23, 2015 at 9:23 PM, Anita Kuno ante...@anteaya.info wrote:
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
On 23 March 2015 at 22:50, Mike Perez thin...@gmail.com wrote:
I've talked to folks at the OpenStack foundation to get feedback on my
communication, and was told this was good, and even better than previous
communication to controversial changes.
I expected nevertheless people to be angry
Dell - Internal Use - Confidential
+2 on Mike’s job
From: Duncan Thomas [mailto:duncan.tho...@gmail.com]
Sent: Tuesday, March 24, 2015 3:07 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Cinder Third-Party CI: what next? (was Re:
[cinder] Request
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
On 03/23/2015 01:50 PM, Mike Perez wrote:
On 12:59 Mon 23 Mar , 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
: [openstack-dev] Cinder Third-Party CI: what next? (was Re:
[cinder] Request exemption for removal of NetApp FC drivers (no voting CI))
On Mon, Mar 23, 2015 at 12:59 PM, Stefano Maffulli
stef...@openstack.orgmailto:stef...@openstack.org wrote:
On Mon, 2015-03-23 at 11:43 -0700, Mike Perez wrote:
We've
: [openstack-dev] Cinder Third-Party CI: what next? (was Re:
[cinder] Request exemption for removal of NetApp FC drivers (no voting CI))
On Mon, Mar 23, 2015 at 12:59 PM, Stefano Maffulli
stef...@openstack.orgmailto:stef...@openstack.org wrote:
On Mon, 2015-03-23 at 11:43 -0700, Mike Perez wrote
On 12:59 Mon 23 Mar , 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
On Mon, Mar 23, 2015 at 12:59 PM, Stefano Maffulli stef...@openstack.org
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
On 21:51 Mon 23 Mar , Rochelle Grober wrote:
I’d like to suggest that the myriad wiki pages and spreadsheets for Third
Party CI also be consolidated to a more manageable count. Just looking for
maintainers contact, you can find information (often conflicting) in
Stackalytics, on the
As an Engineer running the NetApp CI, I thought it would be a good time to
chime in here. While I have many opinions around this whole process, I will
try my best to avoid any judgement and minimize ratholes.
Over the past year, we have implemented a scalable CI system that is now
running tests
22 matches
Mail list logo
