Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of Ewan.Mellor@eu.citrix.com
 designates 62.200.22.115 as permitted sender)
From: Ewan Mellor <Ewan.Mellor@eu.citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Thu, 26 Jul 2012 00:42:33 +0100
Subject: CloudStack 4.0 release plan
Thread-Topic: CloudStack 4.0 release plan
Thread-Index: Ac1qvylvbWtQTlcRRbW3KvklrS5iiQ==
Message-ID: 
 <6005BE083BF501439A84DC3523BAC82DE204F16A7E@LONPMAILBOX01.citrite.net>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_6005BE083BF501439A84DC3523BAC82DE204F16A7ELONPMAILBOX01_"
MIME-Version: 1.0

--_000_6005BE083BF501439A84DC3523BAC82DE204F16A7ELONPMAILBOX01_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

I'm putting together a plan for a CloudStack 4.0 release.  This will be the=
 first release under the Apache (incubated) banner, which is the main reaso=
n for the change in major version number.

This plan is a draft, and your comments are more than welcome.


Development phase: Now - Friday 10 August.
Release branch opens: Monday 13 August.
Stability and bugfix work: Monday 13-Friday 17 August.
Release candidate build: Friday 17 August.
Testing testing testing: Monday 20 - Friday 31 August.
Release: Tuesday 4 September (the day after Labor Day and the week after Li=
nux Foundation's CloudOpen).


In the development phase we still have some library dependencies that we ne=
ed to sort out, so that we can ship an official release without depending o=
n non-Apache-licensed software.  There is a list here: https://cwiki.apache=
.org/confluence/display/CLOUDSTACK/Moving+dependencies+to+ASF+approved+lice=
nses.  Most of this is done now though, and all the major refactoring seems=
 to be under control.

We have a number of feature branches that were taken from the 3.0.x series =
while we were waiting for the dependencies to get sorted out on master, and=
 these are ready to come into mainline.  Now that we know that things are u=
nder control, we should take these and propose them for review and submissi=
on into master.


Once the major features are merged and the dependencies are all sorted out,=
 we should create a 4.0 branch and stabilize (it's been a lot of churn in t=
he past couple of months!).  From the plan above, that gives us 1 week of g=
eneral stability work, plus 2 weeks of testing and iteration on release-can=
didate builds.  I'll be encouraging people to slow down the rate of bugfixe=
s over those last two weeks, so that we can get more stable and give people=
 time to test things in depth.

All being well, this will give us a decent 4.0 release in early September.

Cheers,

Ewan.


--_000_6005BE083BF501439A84DC3523BAC82DE204F16A7ELONPMAILBOX01_--