Also, just to clarify a bit, what I'm mainly wondering about is if we can find a way to make sure our defects are not only trending downward once we get to a certain point in the release, but also approaching zero well in advance of a RC build.
I know Animesh sends out regular updates and I definitely appreciate that he does this. I was just thinking we could come up with a strategy to determine well in advance (on the order of weeks) whether or not a RC candidate build would actually be stable enough to send out into the field. The best way I can think to do this is to make sure Critical and Blocker tickets are down to zero several weeks in advance of an RC build and that we are doing regression testing during that time. Thoughts on this? On Mon, Aug 19, 2013 at 3:22 PM, Mike Tutkowski < mike.tutkow...@solidfire.com> wrote: > What are you thoughts, Animesh, on so many check ins in the final week, > though? I'm just not familiar with a release working like that. Just > curious to get your take on that. Do you feel we have a sufficient number > of automated regression tests in place to catch any new issues? > > > On Mon, Aug 19, 2013 at 3:20 PM, Animesh Chaturvedi < > animesh.chaturv...@citrix.com> wrote: > >> If you look at the Release Dashboard daily trend graph of created v/s >> resolved you will see that we have tapered off significantly this week. I >> have been actively triaging and monitoring issues. >> >> >> > -----Original Message----- >> > From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] >> > Sent: Monday, August 19, 2013 2:15 PM >> > To: dev@cloudstack.apache.org >> > Subject: Re: CloudStack 4.2 Quality Question >> > >> > You can always look at the release dashboard >> > >> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=123209 >> > 42 >> > >> > This is exactly what has been happening >> > >> > Animesh has been sending this out fairly regularly. >> > >> > >> > On 8/19/13 2:01 PM, "Mike Tutkowski" <mike.tutkow...@solidfire.com> >> > wrote: >> > >> > >I think we need some kind of process in place to monitor the number of >> > >critical and blocker defects over the course of the release and make >> > >sure they're tapering off as we approach a RC build. >> > > >> > >My main comment about this release (this is the first CS release that >> > >I've participated in) is that I've never seen 150 bugs get fixed in the >> > >final week. >> > > >> > >At any of the commercial companies I've worked at over the past 15 >> > >years (SolidFire, HP, LeftHand Networks, Agilent Technologies, >> > >Accenture), checking in more than a small handful of defects at the >> > "last minute" >> > >would >> > >not be likely to happen. If we would absolutely need to do this, the >> > >release would have to be pushed out so that we could regression test it >> > >properly. >> > > >> > >The main point is that we cannot compromise CloudStack's quality just >> > >to meet a release deadline. I'm guessing people agree with that. >> > > >> > > >> > >On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski < >> > >mike.tutkow...@solidfire.com> wrote: >> > > >> > >> "it is" meaning "premature" >> > >> >> > >> >> > >> On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski < >> > >> mike.tutkow...@solidfire.com> wrote: >> > >> >> > >>> I still believe it is, but the VMware "problem" was my fault - I >> > >>>must not have had nonoss on b/c it works now. :) >> > >>> >> > >>> >> > >>> On Mon, Aug 19, 2013 at 2:44 PM, Chip Childers >> > >>><chip.child...@sungard.com >> > >>> > wrote: >> > >>> >> > >>>> On Mon, Aug 19, 2013 at 02:33:33PM -0600, Mike Tutkowski wrote: >> > >>>> > Looks like we have serious issues as of today in 4.2 (I've >> > >>>> > noticed >> > >>>> > DevCloud2 not working and VMware support is broken) (aside from >> > >>>>plenty >> > >>>> of >> > >>>> > blocker defects still to be completed). >> > >>>> > >> > >>>> > When do we start talking about how the 4.2 RC build is not going >> > >>>> > to >> > >>>> happen >> > >>>> > until the codebase calms down a bit? I have serious doubts that >> > >>>> > 4.2 >> > >>>>is >> > >>>> > ready this week. >> > >>>> > >> > >>>> > Thoughts? >> > >>>> >> > >>>> Agreed - It seems that this first RC might be a bit premature. >> > >>>> >> > >>> >> > >>> >> > >>> >> > >>> -- >> > >>> *Mike Tutkowski* >> > >>> *Senior CloudStack Developer, SolidFire Inc.* >> > >>> e: mike.tutkow...@solidfire.com >> > >>> o: 303.746.7302 >> > >>> Advancing the way the world uses the >> > >>>cloud<http://solidfire.com/solution/overview/?video=play> >> > >>> * * >> > >>> >> > >> >> > >> >> > >> >> > >> -- >> > >> *Mike Tutkowski* >> > >> *Senior CloudStack Developer, SolidFire Inc.* >> > >> e: mike.tutkow...@solidfire.com >> > >> o: 303.746.7302 >> > >> Advancing the way the world uses the >> > >>cloud<http://solidfire.com/solution/overview/?video=play> >> > >> * * >> > >> >> > > >> > > >> > > >> > >-- >> > >*Mike Tutkowski* >> > >*Senior CloudStack Developer, SolidFire Inc.* >> > >e: mike.tutkow...@solidfire.com >> > >o: 303.746.7302 >> > >Advancing the way the world uses the >> > >cloud<http://solidfire.com/solution/overview/?video=play> >> > >* * >> >> > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the > cloud<http://solidfire.com/solution/overview/?video=play> > *™* > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *™*
