> -----Original Message-----
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Friday, October 12, 2012 2:03 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ASFCS40] Getting to the next VOTE round...
> 
> I just closed CLOUDSTACK-326
> 
> David is looking at CLOUDSTACK-329
> 
> I'm hopefully someone will resolve CLOUDSTACK-325, but I'm not sure if
> anyone is working on it.  I'm not going to wait for this one though.


CLOUDSTACK-325 is fixed: commit 4903535959f844865a602469247a61e2d5dd9fb9 on 4.0 
branch, only one line change, don't need to retest.

> 
> If David clears 329 before I check back in tonight, I'm going to cut
> another RC tonight and start round 2 voting.  Otherwise, I'll probably
> have to wait until either another evening this weekend, or on Monday.
> 
> -chip
> 
> On Fri, Oct 12, 2012 at 4:59 PM, Will Chan <will.c...@citrix.com> wrote:
> > Chip,
> >
> > I assume the two outstanding issues are being looked at by someone?
> >
> > Will
> >
> >> -----Original Message-----
> >> From: Chip Childers [mailto:chip.child...@sungard.com]
> >> Sent: Friday, October 12, 2012 1:21 PM
> >> To: cloudstack-dev@incubator.apache.org
> >> Subject: Re: [ASFCS40] Getting to the next VOTE round...
> >>
> >> On Fri, Oct 12, 2012 at 4:06 PM, Chip Childers
> >> <chip.child...@sungard.com> wrote:
> >> > Hi all,
> >> >
> >> > Great progress today in getting closer to another round of voting
> for
> >> > 4.0.0-incubating!
> >> >
> >> > AFAIK, CLOUDSTACK-326 (README, NOTICE and LICENSE file issues) is
> the
> >> > outstanding *required* fix.
> >> >
> >> > There is talk of correcting CLOUDSTACK-325 ("AWS API - Port 7080
> is
> >> > not opened by default..."), but it needs to be corrected in master.
> >> > I'm not going to hold up the release candidate build for this fix
> >> > though.
> >> >
> >> > As soon as we're able to come to a conclusion, I'll do another
> build
> >> > and start the VOTE again.
> >> >
> >> > Thanks all!
> >> >
> >> > -chip
> >>
> >> One additional issue:  CLOUDSTACK-329 "Can't create rpms/debs from
> >> source tarball"
> >>
> >> That one also needs to be resolved.
> >

Reply via email to