H Mike, Make sure you write plenty of unit tests for whatever methods you need for the features you are implementing. You can not exaggerate for a while. Coverage is behind quite a bit and I am not a betting man, so I bet there is going to be a 4.2.1.
In short: I share your concern. Daan On Thu, Aug 15, 2013 at 9:28 PM, Sudha Ponnaganti <sudha.ponnaga...@citrix.com> wrote: > Mike, > > I have similar concern as well. > > We have regression and BVT tests running daily on 4.2 branch locally besides > manual validation of the defects and impacted areas. Even though we would not > be able to catch all the issues, several regressions were caught and you can > see the defects by using [Automation] in subject line for 4.2. This type of > turnaround is quite uncommon for releases but 4.2 has too many features and > some of the feature implementation has been done very late which is causing > high inflow. All fixes should be coming in for Critical and blocker defects > only at this point. > > Thanks > /Sudha > > -----Original Message----- > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > Sent: Thursday, August 15, 2013 12:02 PM > To: dev@cloudstack.apache.org > Subject: CloudStack 4.2 Quality Question > > Hi everyone, > > I've only been working on CS for about 8 months now, so I don't have a lot of > experience with the way releases go. > > My question is this: I've noticed over 100 commits to 4.2 since Monday (one > week from a potential release of the product). Is this normal? Unless we have > a super great suite of automated regression tests, it makes me concerned > about the potential quality of the product. > > Any thoughts on this? > > Thanks! > > -- > *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> > *(tm)*
