Ah, cool. Thanks. The reason I picked this out is that the language concerned me. Releases are decided by the community. So in some instances, it can take weeks (or longer) to get a release out of the door. (This is rare, but can happen if there are problems identified.) There is nothing wrong in setting targets. In fact, that's a very good thing. But ultimately, the community decides the release date when they successfully vote for a release artefact. :)
Thanks, On Mon, Oct 1, 2012 at 12:07 AM, Sudha Ponnaganti < [email protected]> wrote: > Noah, > > Here is the mail thread that shows dates that have been proposed and > formalized - > http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201207.mbox/%3c6005be083bf501439a84dc3523bac82de204f16...@lonpmailbox01.citrite.net%3E > > Since then we have delays and I couldn't locate the update on this mail > thread which shows new date of Oct 5th. But that is the date we are > executing against. > > In any case I would think this need to be reviewed unless we have > addressed all open issues by Monday AM PST. > > Thanks > /Sudha > > -----Original Message----- > From: Noah Slater [mailto:[email protected]] > Sent: Sunday, September 30, 2012 9:47 AM > To: [email protected] > Subject: Re: [ASFCS40) Pending defect fixes and Closure of QA cycle > > Who set the "official date"? > > There is a good chance the release will fail the first few votes, and each > iteration can take 72 hours. > > On Fri, Sep 28, 2012 at 3:34 PM, Sudha Ponnaganti < > [email protected]> wrote: > > > Hi Team, > > > > We are supposed to close QA cycle today but given the pending defects > > some validation is spilling over. Defects have been shared through > > JIRA > > > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&j > > qlQuery=project+%3D+CLOUDSTACK+AND+resolution+%3D+Unresolved+AND+fixVe > > rsion+in+%28EMPTY%2C+12323251%2C+12323252%29+ORDER+BY+priority+DESC > > > > Pl review blockers and critical defects assigned to you and respond back. > > There are at least 20 of such issues exist. Need to review these daily > > and burn them down to 0 before we cut final RC Candidate ( official > > date of oct 5th is at risk now). > > > > I will post latest metrics by EOD today on pending tasks to close > > cycle https://cwiki.apache.org/CLOUDSTACK/asf-cs-40-qa-metrics.html > > > > Release team - can we have call daily ( IRC) to review pending items > > and see how we can bring closure to the release cycle. > > > > Thanks for your cooperation > > > > Thanks > > /Sudha > > > > > > -- > NS > -- NS
