On Tue, Feb 7, 2017 at 7:34 AM, Andrea Frittoli
wrote:
>
> On Tue, Feb 7, 2017 at 1:55 AM Ghanshyam Mann
> wrote:
>
>> Hi Jordan,
>>
>> Thanks for bring it up. I know we had both side of argument on those
>> changes.
>>
>> IMO in general, its all QA team responsibility to verify the requirement
On Tue, Feb 7, 2017 at 1:55 AM Ghanshyam Mann
wrote:
> Hi Jordan,
>
> Thanks for bring it up. I know we had both side of argument on those
> changes.
>
> IMO in general, its all QA team responsibility to verify the requirement
> very strictly and make sure no changes break existing released versi
Hi Jordan,
Thanks for bring it up. I know we had both side of argument on those
changes.
IMO in general, its all QA team responsibility to verify the requirement
very strictly and make sure no changes break existing released version and
so users. Many times QA team does not agree to development t
Hi gmann,
Thanks for your candidacy. Let me ask one question if it's not too
late. What's the role of the QA team when it comes to API change ? I
have in mind the recent Glance change related to private vs shared
image status.
Someone in our community asked :
* "I need to get an official decision
Hi All,
First and foremost would like to wish you all a successful 2017 ahead and with
this I'm announcing my PTL candidacy of the Quality Assurance team for the Pike
release cycle.
I am glad to work in OpenStack community and would like to thank all the
contributors who supported me to explor