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 will.chan@citrix.com
 designates 66.165.176.63 as permitted sender)
From: Will Chan <will.chan@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Tue, 9 Oct 2012 12:18:45 -0700
Subject: RE: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Thread-Topic: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
Thread-Index: Ac2mIy/hEldn2lQsQcuRpOvLFLzaYwALjfig
Message-ID: 
 <61AE1E2837A06D4A8E98B796183842D40129322E86D1@SJCPMAILBOX01.citrite.net>
References: 
 <CA+96GG6p3BSAUh_SYdVP+ir6hj1hoNspaaL=gPDWJ5BsNBx5Uw@mail.gmail.com>
In-Reply-To: 
 <CA+96GG6p3BSAUh_SYdVP+ir6hj1hoNspaaL=gPDWJ5BsNBx5Uw@mail.gmail.com>
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

>From this list, it looks like we have two blockers left.

1. Adding deb package for AWSAPI.  Edison said he'll look into this and QA =
for this should be pretty simple.
2. CLOUDSTACK-301. This is the Cisco Nexus vSwitch support that CloudPlatfo=
rm recently GAed in our 3.0.5 release (Burbank).  It look like with the rec=
ent changes to the plugin framework, the porting of the feature was not don=
e well.  The time to fix this and to QA it properly could be in the order o=
f days or perhaps a week.  I would hate to delay the release of CloudStack =
anymore due to this one feature.  What does the community think?  Do you th=
ink we should drop this and release 4.0?  I believe we have a couple of oth=
er features that are in similar situations (i.e. Netscalar autoscaling, but=
 I could be wrong).

Will

> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Tuesday, October 09, 2012 6:36 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: [ASFCS40] Status (Oct 9) of starting a 4.0.0 vote
>=20
> Hi all,
>=20
> Lots of things are happening right now around 4.0.0, so we're still not r=
eady
> to VOTE.
>=20
> Here's a summary of the outstanding issues (as I see them):
>=20
> * AWASPI was integrated to quickly, and some things were missed.  The
> thread Wido started on it's appropriateness needs to come to consensus.  =
If
> it does stay, it needs the DEB packaging to be completed and tested
> (CLOUDSTACK-294).  Wido is willing to do the packaging after consensus is
> reached.
>=20
> * CLOUDSTACK-301 is a blocker as well - That one looks like there is miss=
ing
> code?  Devdeep Singh is the assigned community member.
>=20
> * CLOUDSTACK-156 is a blocker that was reopened.  Rohit, can you work
> with the test team to get it resolved / closed?
>=20
> * CLOUDSTACK-298 is set as Critical.  Can someone triage that bug and
> make a recommendation as to the severity and timing of a fix?  It's
> currently unassigned.
>=20
> * The release notes need to be pulled in from
> https://reviews.apache.org/r/7498/  I'll take responsibility for doing th=
at
> today.
>=20
> * We didn't pull the internationalization resources into 4.0 (they were
> committed to master last night by David).  I'd suggest we hold of on putt=
ing
> them in the 4.0 branch, but that we use master to build the project's
> documentation site.
>=20
> That's all I have on my list right now.  Shout if there are any other iss=
ues,
> and PLEASE get involved in reaching conclusions to the issues noted above=
.
>=20
> -chip