On Mon, Jan 7, 2013 at 12:39 PM, Alex Huang <[email protected]> wrote: > 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 this > 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 ends 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.
+1 to this proposal. I'd actually love it, as I'm currently struggling to figure out how to track this manually for now. If someone has the time to get it implemented, I'm all for that. > --Alex > >> -----Original Message----- >> From: Chip Childers [mailto:[email protected]] >> Sent: Thursday, January 03, 2013 1:51 PM >> To: [email protected] >> Subject: Re: [DISCUSS] Adding new features to CloudStack >> >> On Tue, Dec 11, 2012 at 7:18 PM, Animesh Chaturvedi >> <[email protected]> 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 process >> > 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 >> > >> > >> > >> >> This was never answered, but see the discussion here: >> http://markmail.org/message/hh3jprj4pjvwe6xr >
