Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of Alex.Huang@citrix.com
 designates 66.165.176.63 as permitted sender)
From: Alex Huang <Alex.Huang@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Fri, 21 Sep 2012 10:25:42 -0700
Subject: RE: [ASFCS40] Features that did not make the release...
Thread-Topic: [ASFCS40] Features that did not make the release...
Thread-Index: Ac2YHMA9GXaEzKQ1RI6XZRYThtZ/uAAARKJA
Message-ID: 
 <B1DF26ECC0458748AC97CECE2DA98D41012FA04509C6@SJCPMAILBOX01.citrite.net>
References: 
 <B1DF26ECC0458748AC97CECE2DA98D41012FA0450999@SJCPMAILBOX01.citrite.net>
 <505CA0A5.40603@widodh.nl>
In-Reply-To: <505CA0A5.40603@widodh.nl>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


> -----Original Message-----
> From: Wido den Hollander [mailto:wido@widodh.nl]
> Sent: Friday, September 21, 2012 10:15 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ASFCS40] Features that did not make the release...
>=20
>=20
>=20
> On 09/21/2012 06:24 PM, Alex Huang wrote:
> > There are two features that did not make the 4.0 release: autoscaling a=
nd
> brocade.  Significant code changes are expected for both of these feature=
s
> past the code freeze and we just couldn't risk the disruption to the QA c=
ycle.
> >
> > Please comment.
> >
>=20
> IIRC these features didn't make the initial window anyway. Now, I don't w=
ant
> to play it that hard, but I think we've got our hands full for getting 4.=
0 out of
> the door in a stable matter.
>=20
> 4.1 is the first version they should get into, but imho the priority it w=
ith
> getting a 4.0 final release out of the door which is stable enough for pe=
ople
> to use in production.
>=20

+1.  I'm pointing it out mainly because I don't recall there was anything s=
ent out regarding it.  We also may want to discuss whether or not there's a=
 good process we should go through to determine what features made it.  For=
 example, it probably should have been the first thing to do when we decide=
d on the code freeze of the release.

--Alex