[OpenStack-Infra] [cinder] I will add Dorado and T CI within one week if I can't revome Dorado and T driver

2015-03-19 Thread liuxinguo
Hi Mike, * Maybe I have a misunderstand of the warning you said that all drivers must have a CI. I have taken that as if the Dorado and T driver did not have a CI then the Dorado and T driver will be removed from the community individually. If I can't remove Dorado and T driver individ

Re: [OpenStack-Infra] enforce bug ids in commit message

2015-03-19 Thread Robert Collins
On 19 March 2015 at 20:57, Vinay Mahuli wrote: > We wanted to do this only for release branches where we want to enforce bug > ids. > > We have similar setup like openstack gerrit, and hence we need this info to > implement this change. > > Any ideas on how to make this change? Ah, if you want th

Re: [OpenStack-Infra] enforce bug ids in commit message

2015-03-19 Thread Robert Collins
On 19 March 2015 at 18:58, wrote: > Dell - Internal Use - Confidential > > I agree with Jeremy. My approach has been if it's addressing a problem or it > is a significant enough change that needs some additional background beyond > what can be put in a commit message then it makes sense to crea

[OpenStack-Infra] [cinder] May you reconsider about huawei driver?

2015-03-19 Thread liuxinguo
Hi Mike, I have seen the patch at https://review.openstack.org/#/c/165990/ saying that huawei driver will be removed because “the maintainer does not have a CI reporting to ensure their driver integration is successful”. But in fact we really have a CI months ago and it is really reporting to

Re: [OpenStack-Infra] Fwd: Zanata 3.6.0

2015-03-19 Thread Paul Carlton
Thanks Paul Carlton Software Engineer Cloud Services Hewlett Packard BUK03:T242 Longdown Avenue Stoke Gifford Bristol BS34 8QZ Office: +44 (0)117 316 2189 Mobile:+44 (0)7768 994283 Email:mailto:paul.carlt...@hp.com Hewlett-Packard Limited registered Office: Cain Road, Bracknell, Berk

Re: [OpenStack-Infra] enforce bug ids in commit message

2015-03-19 Thread Vinay Mahuli
We wanted to do this only for release branches where we want to enforce bug ids. We have similar setup like openstack gerrit, and hence we need this info to implement this change. Any ideas on how to make this change? Regards, Vinay On Thu, Mar 19, 2015 at 1:17 PM, Andreas Jaeger wrote: > O

[OpenStack-Infra] Fwd: Zanata 3.6.0

2015-03-19 Thread Elizabeth K. Joseph
Hi everyone, As noted in the spec[0], Zanata works to release every 3 months, and it's been that long since we started the patch to bring it into puppet in our infrastructure. As such, there's a new release that we should be focusing on: 3.6.0. See below from Carlos for details, particularly of n

Re: [OpenStack-Infra] enforce bug ids in commit message

2015-03-19 Thread Andreas Jaeger
On 03/18/2015 12:08 PM, Vinay Mahuli wrote: > Hi, > > How to enforce users to put the "bug ids" in the review commits ? > A user shouldn't be able to raise a review request if the user hasn't > put the corresponding "bug id" in the commit message. AFAIK this is not a requirement in most (all?) pr