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 on in the past 15 years experienced such a high
volume of fixes so late in the game).

People did chime in both in agreement and also to try to soothe my concerns.

In the end, I just wanted to wait and see how this process plays out, so I
didn't feel I should cast a vote.

I hope that clarifies my thinking here.

Thanks


On Tue, Sep 10, 2013 at 2:48 PM, Sebastien Goasguen <run...@gmail.com>wrote:

> I am changing the subject of the [RESULTS] thread for the 4.2 release.
>
> On Sep 10, 2013, at 4:12 PM, Animesh Chaturvedi <
> animesh.chaturv...@citrix.com> wrote:
>
> >
> >
> > 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 does not matter, the
> number of people voting is worrisome to me.
>
> We have over ~70 apache committers on CloudStack, why didn't people vote ?
>
> -sebastien
>
> > I'm going to proceed with moving the release into the distribution repo
> now and work on release notes and other documentation tasks
> >
> > The -1 are recorded for the CLVM issue [1]. A fix for this issue is
> available and fixed in 4.2-forward branch and will be available for  4.2.1.
> If anyone needs the fix now they can cherry-pick from 4.2-forward with
> commitId f2c5b5fbfe45196dfad2821fca513ddd6efa25c9. This issue will be
> release noted.
> >
> >
> > [1] https://issues.apache.org/jira/browse/CLOUDSTACK-4618
> >
> >
> > Thanks
> > Animesh
>
>


-- 
*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>
*™*

Reply via email to