Re: So few votes on the 4.2 release

2013-09-10 Thread Mike Tutkowski
Oh, and to be clear, I don't think anyone is criticizing Animesh's efforts. He does a great job of keeping track of defect trends and informing the community. Let me provide an example for how we did this at HP/LeftHand, which is where I worked on a clustered SAN technology for seven years before

Re: So few votes on the 4.2 release

2013-09-10 Thread David Nalley
>> >> The vote has *passed* with the following results (binding PMC votes >> indicated with a "*" next to their name: >> >> +1 : Edison*, Chiradeep*, Sebastien*, Prasanna*, Rajesh Batala, Ove Ewerlid >> -1 : Marcus*, Chip*, Simon Weller >> > > FWIW, I am very disappointed by this vote. The result

Re: So few votes on the 4.2 release

2013-09-10 Thread Marcus Sorensen
>From my point of view, it's hard to 'buy off' on something that has such a large scope. In the past I've been skiddish to cast a vote, knowing that I've only tested the things I'm familiar with and I may very well be casting a +1 for something completely broken. The irony is that I don't think a

Re: So few votes on the 4.2 release

2013-09-10 Thread Mike Tutkowski
Yep, I agree it's a tight schedule. Whether or not that's a good idea is beside the point, I suppose. I also agree some last-minute changes will come in. I was simply pointing out that I have never encountered over 200 fixes coming into a release in the final couple weeks. On a project where regre

Re: So few votes on the 4.2 release

2013-09-10 Thread Chiradeep Vittal
The process is laid out. There's exactly 2 months of testing/bug fixing. Given that schedule it isn't unreasonable that there are last minute fixes. Since the release manager is not an expert on any one feature, he/she cannot judge which fixes should/shouldn't make it into the release. The RM onl

Re: So few votes on the 4.2 release

2013-09-10 Thread Daan Hoogland
Sebastien, I could/would have voted +0 as I don't have a clear picture of the quality of the release. this once again comes down to testing in 72 hour and automating it. Daan On Tue, Sep 10, 2013 at 10:48 PM, Sebastien Goasguen wrote: > I am changing the subject of the [RESULTS] thread for the

Re: So few votes on the 4.2 release

2013-09-10 Thread Mike Tutkowski
Hi Sebastien, Personally I felt like I just didn't yet understand our testing/QA process enough to know if 4.2 was ready or not. I did voice concerns over the past few weeks regarding the number of checkins that took place right before a RC was built (since I have never on any product I've worked

So few votes on the 4.2 release

2013-09-10 Thread Sebastien Goasguen
I am changing the subject of the [RESULTS] thread for the 4.2 release. On Sep 10, 2013, at 4:12 PM, Animesh Chaturvedi wrote: > > > The vote has *passed* with the following results (binding PMC votes indicated > with a "*" next to their name: > > +1 : Edison*, Chiradeep*, Sebastien*, Prasan