We are already in defect fix mode right?? ( even though blockers took longer time to get resolved which prevented QA to make good progress) Now we are getting features blockers but not QA blockers i.e only few feature validation is blocked but QA is making progress on rest of features.
-----Original Message----- From: Sebastien Goasguen [mailto:run...@gmail.com] Sent: Wednesday, March 06, 2013 2:15 AM To: cloudstack-dev@incubator.apache.org Subject: Re: [QA][DISCUSS] Should we document formal release criteria? On Mar 5, 2013, at 2:18 PM, Joe Brockmeier <j...@zonker.net> wrote: > On Tue, Mar 5, 2013, at 01:14 PM, Chip Childers wrote: >> On Tue, Mar 05, 2013 at 11:11:51AM -0800, Alex Huang wrote: >>> So in this definition, MAJOR and above must be fixed before a release is >>> cut? >> >> Personally, I've used the "no blockers and <5 critical with work >> arounds" as the criteria, using the definitions I offered. > > How many "Major" bugs are acceptable? Currently we have 187. Even if > they're not going to completely disrupt use of the platform, it seems > to me that releasing with >100 major bugs is a bit much. Bit off-thread, but could we have a bug sprint ? > > Best, > > jzb > -- > Joe Brockmeier > j...@zonker.net > Twitter: @jzb > http://www.dissociatedpress.net/
