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 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>
CC: Animesh Chaturvedi <animesh.chaturvedi@citrix.com>
Date: Mon, 7 Jan 2013 09:39:05 -0800
Subject: RE: [DISCUSS] Adding new features to CloudStack
Thread-Topic: [DISCUSS] Adding new features to CloudStack
Thread-Index: Ac3p/G9ApSFYqWSIRT2/Jk25LDQ+kgC///RQ
Message-ID: 
 <B1DF26ECC0458748AC97CECE2DA98D41012FA385EBB3@SJCPMAILBOX01.citrite.net>
References: 
 <7A92FF96DF135843B4B608FB576BFC3E012DA27F41B8@SJCPMAILBOX01.citrite.net>
 <CA+96GG5bbGbEj-X8DOS3oqhuruyxjM8GTJ4QtkQo3t0gX5gkzw@mail.gmail.com>
In-Reply-To: 
 <CA+96GG5bbGbEj-X8DOS3oqhuruyxjM8GTJ4QtkQo3t0gX5gkzw@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

Animesh,

The mail thread that Chip is referring to has not been wrapped up.  Can you=
 help in terms of wrapping it up?

I don't see mail responses opposing it.  I think the major issue was is thi=
s too much work for the release manager from Mohammad.  I generally believe=
 it is actually less work for a release manager to have a good view of the =
status of the bugs rather than keep searching through email which often end=
s without any conclusive resolutions on the current status of the bug.

If there are no strong objections, then we should work with apache infra to=
 implement this workflow.

--Alex

> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Thursday, January 03, 2013 1:51 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Adding new features to CloudStack
>=20
> On Tue, Dec 11, 2012 at 7:18 PM, Animesh Chaturvedi
> <animesh.chaturvedi@citrix.com> wrote:
> > Folks
> >
> > I was reviewing the wiki on Adding New Features
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Adding+new+fe
> atures+and+design+documents to Cloudstack, and I was wondering that  a
> feature proposal can come from a user who is not necessary planning to
> develop it themselves.
> >
> > In order to encourage folks like that, will it help to clarify the proc=
ess on
> how can a developer signup for such a feature? How about formalizing a 2-=
3
> day time frame to community to sign up for a feature once it is proposed?=
 If
> there are multiple signup it's up to the signees to work collaboratively =
or
> resolve between themselves.
> >
> >
> > Thanks
> > Animesh
> >
> >
> >
>=20
> This was never answered, but see the discussion here:
> http://markmail.org/message/hh3jprj4pjvwe6xr