Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <6005BE083BF501439A84DC3523BAC82DE44D7E43EF@LONPMAILBOX01.citrite.net>
References: 
 <CA+96GG7AOBifK-WGGMkbd3oo+wPsc4kNm=zSLsESNjWXs0bgBA@mail.gmail.com>
 <53AEFEE9DD31EF42ADDDAD0125BCD52DD726AC2EC8@LONPMAILBOX01.citrite.net>
 <6005BE083BF501439A84DC3523BAC82DE44D7E43EC@LONPMAILBOX01.citrite.net>
 <8958392355476010626@unknownmsgid>
 <6005BE083BF501439A84DC3523BAC82DE44D7E43EF@LONPMAILBOX01.citrite.net>
From: David Nalley <david@gnsa.us>
Date: Fri, 10 Aug 2012 23:00:45 -0400
Message-ID: 
 <CAKprHVZCPVUR9HRRWnqiYDPg7Gk8r8T3tUkFWLB9h9_zs33MZg@mail.gmail.com>
Subject: Re: Release Management Process
To: cloudstack-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+Release+Checklist
>
> Ewan.
>

So there are a few timeline problems here.
The project has to vote - that stays open for 72 hours. (e.g.
annointing a release candidate)  Once that vote concludes we then move
to getting IPMC approval, and that vote is for a minimum of 72 hours
That's effectively a week added to this schedule.

Also, and  I think this is accounted for in your schedule, but we have
to allow at least 24 hours to elapse between our uploading of the bits
and our release.

--David