> -----Original Message----- > From: Chip Childers [mailto:chip.child...@sungard.com] > Sent: Tuesday, August 27, 2013 10:12 AM > To: dev@cloudstack.apache.org > Subject: Re: [VOTE] Apache CloudStack 4.2.0 (second round) > > On Tue, Aug 27, 2013 at 05:46:24PM +0200, Wido den Hollander wrote: > > > > > > On 08/27/2013 05:20 PM, Chip Childers wrote: > > >On Tue, Aug 27, 2013 at 02:29:51PM +0000, Animesh Chaturvedi wrote: > > >> > > >> > > >>>>Git Branch and Commit SH: > > >>>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlo > > >>>>g;h= > > >>>>refs/heads/4.2 > > >>>>Commit: 9103984d349927a87b0683048dda2d8004e6854f > > >>>> > > >>> > > >>>I notice Edison's fix is missing although it is on 4.2. Is this > > >>>intended? > > >>> > > >> [Animesh>] Edison checked it in after I cut the RC and I did not > receive any request for him to pick this fix. The fix seems like a trial > and best to be verified. I will continue with this RC. > > >> > > > > > >Animesh, > > > > > >I personally don't think that we are in a position for this second > > >round. There are a few outstanding threads (Wido's last cherry-pick > > >request is an example) that seem like they need to be sorted before > > >we go again. > > > > > > > I was about to vote -1 due to the bug I encountered. > > > > I personally have the feeling 4.2 isn't ready yet and it needs some > > more ironing to squash more bugs and more testing. > > > > If QA came up with bugs just last week, how we can release now? I > > haven't been able to do all the testing I wanted. > > To be clear, my personal take was that there were *known* fixes coming > in via the mailing list that needed to be considered for inclusion. > I wasn't advocating another round of QA (outside of RC testing). > > > [Animesh>] I had included all the cherry-pick request that came until that time, Wido had mentioned yesterday in the prior VOTE thread that CLOUDSTACK-4423 is probably fixed already so I went ahead with building RC.
I can pick up the requested cherry-picks and rebuild another RC and restart the VOTE. I am trying best to stick to time based release and I feel we have to draw a line somewhere where we say remaining fixes will come in 4.2.1 unless the issues are with core orchestration layer. > > Wido > > > > >Given that, since this is a formal VOTE request, I'm -1 (binding). > > >I'd like to see the outstanding cherry-picks occur, and for any lose > > >threads to be brought to a close. > > > > >
