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 release. Otherwise the quality process wouldn't make sense.
On 31-Jul-2015, at 4:26 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > On Fri, Jul 31, 2015 at 12:45 PM, Raja Pullela <raja.pull...@citrix.com> > 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 single person decision > but needs to be discussed. > > -- > Daan
