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 Edison.su@citrix.com
 designates 66.165.176.89 as permitted sender)
From: Edison Su <Edison.su@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Fri, 26 Oct 2012 13:07:38 -0700
Subject: RE: Moving beyond 4.0.0-incubating
Thread-Topic: Moving beyond 4.0.0-incubating
Thread-Index: Ac2yMohYxMPqpw8KQvScU424OqeQmQBgrCCw
Message-ID: 
 <C66C814C1ABFA8449FF65CB44953A8B4012CBB65BE65@SJCPMAILBOX01.citrite.net>
References: 
 <CA+96GG5r8TaghjL2ZTQs8vzFh9z1ms2Vibru1rJvksG+NV_P2w@mail.gmail.com>
In-Reply-To: 
 <CA+96GG5r8TaghjL2ZTQs8vzFh9z1ms2Vibru1rJvksG+NV_P2w@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

I am working on the storage subsystem refactor on javelin branch. The code =
I write is under platform/storage directory. I'll send out a detailed chang=
es I want to make in the next few days.

> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Wednesday, October 24, 2012 2:57 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Moving beyond 4.0.0-incubating
>=20
> Hi all,
>=20
> Obviously we still have to actually pass a vote, and then pass another
> vote within the IPMC, before we can call success with
> 4.0.0-incubating.  (And we may have to do this several more times,
> depending on how things go.)  However, I think it's time to catch up
> on work that's ongoing, ideas for what to do next, and to start to
> plan out what our next community goals are.
>=20
> Along those lines, perhaps we can all start communicating a little
> better about where other work stands?  I'd like to ask folks that are
> working on features / tools to kick off discussion threads for their
> specific areas.  Questions that would be great to have answered
> include:  How's the work going generally?  Are there any design
> decisions that should be talked about?  Any help needed?
>=20
> Examples that come to mind (in no order, and not exhaustive):
>=20
> 1- Adding more plugin capabilities to the core design (I assume this
> is what the javelin branch is for)
> 2- RBAC
> 3 - Event handling / message bus integration
> 4 - DevCloud changes
> 5 - Work demonstrated at Citrix Synergy (Cisco product integrations)
> 6 - Auto-scaling
> 7 - Host deployment feature
>=20
> I'd also like to ask that we start proposing new features to the list
> again (I know that some of this has continued, but I think it died
> down a bit).  It's going to be important to start thinking about
> timing of our next feature release soon (and to be time bound about
> it), so I think we need to ensure that we're all sharing current
> thoughts, status, etc...  And as always, feel free to let me know if
> you disagree!
>=20
> Thanks all,
>=20
> -chip