Koushik,
If an issue is serious it will be easy enough to convince the rest of
us that this is so.
On Fri, Jul 31, 2015 at 4:48 PM, Koushik Das wrote:
> Currently we are putting in effort to make sure no commit goes in directly
> without a PR. Based on that, I think it makes sense to treat any
Currently we are putting in effort to make sure no commit goes in directly
without a PR. Based on that, I think it makes sense to treat any reported
regression bug as a release blocker. If the bug is reported after release then
it is a different issue and needs to be fixed in the subsequent rele
llela [mailto:raja.pull...@citrix.com]
Sent: Friday, July 31, 2015 4:42 PM
To: dev@cloudstack.apache.org
Subject: RE: Raised a blocker bug for failure in Add Region
Ok, thanks for the clarification Daan...
Can someone, who is testing/trying out 4.6, test this functionality and post
their fin
blocker bug for failure in Add Region
On Fri, Jul 31, 2015 at 12:45 PM, Raja Pullela wrote:
> I feel this is a Blocker bug, failing across all Hypervisors, - not sure, the
> reason for being it downgraded to a Critical.
because it was not discussed on list before marking it as blocker. a b
On Fri, Jul 31, 2015 at 12:45 PM, Raja Pullela wrote:
> I feel this is a Blocker bug, failing across all Hypervisors, - not sure, the
> reason for being it downgraded to a Critical.
because it was not discussed on list before marking it as blocker. a
blocker is blocking a release which is not a
@cloudstack.apache.org
Subject: RE: Raised a blocker bug for failure in Add Region
I am seeing the same issue on all the Automation BVT runs (across all
Hypervisors - KVM, XS and VMWare)- will publish automation results summary on
CWIKI and will post the same here
I am seeing the same issue on all the Automation BVT runs (across all
Hypervisors - KVM, XS and VMWare)- will publish automation results summary on
CWIKI and will post the same here.
integration.smoke.test_regions.TestRegions.test_createRegion is where it is
failing.
-Original Message--
