cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Animesh Chaturvedi <animesh.chaturv...@citrix.com>
Subject RE: CloudStack 4.2 Quality Question
Date Mon, 19 Aug 2013 21:20:58 GMT
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.Vittal@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.tutkowski@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.tutkowski@solidfire.com> wrote:
> >
> >> "it is" meaning "premature"
> >>
> >>
> >> On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski <
> >> mike.tutkowski@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.childers@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.tutkowski@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.tutkowski@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.tutkowski@solidfire.com
> >o: 303.746.7302
> >Advancing the way the world uses the
> >cloud<http://solidfire.com/solution/overview/?video=play>
> >**


Mime
View raw message