> -----Original Message----- > From: Chip Childers [mailto:chip.child...@sungard.com] > Sent: Thursday, November 01, 2012 5:09 PM > To: cloudstack-dev@incubator.apache.org > Subject: Re: new features > > On Thu, Nov 1, 2012 at 6:20 PM, Chiradeep Vittal < > chiradeep.vit...@citrix.com> wrote: > > Probably the best answer is all 3: dev list, Jira and wiki Dev List > > because "if it didn't happen on the ML it didn't happen at all" > > Jira : for trackability > > Wiki: for detailed "living" design docs. > > Yup. Absolutely. > > We should probably try to get organized around that model. > > > On 11/1/12 3:09 PM, "Joe Brockmeier" <j...@zonker.net> wrote: > > > >>On Thu, Nov 1, 2012, at 01:49 PM, Jie Feng wrote: > >>> There seem to be a few places where new feature requests come up: > >>> CloudStack user mailing list, CloudStack dev mailing list, the two > >>>sites Chiradeep mentioned below, and JIRA. Is there a guideline for > >>>what to do if we have a new feature request? Ideally, all the > >>>discussions for a specific request should be tracked somewhere, so > >>>that people can continue to comment on it until implemented. Also, > >>>it would be nice if there is a central place developer can go to see > >>>the feature requests and pick up the ones they want to work on, and > >>>users can see when it will be implemented. I wonder how other Apache > >>>project deals with this. > >> > >>Jira would be the best place for these. An "Improvement" ticket would > >>be ideal for any new features or enhancements. >
There is a ticket type called "New Feature." If we want to use Improvement for new features, we should remove the New Feature type, as it will cause confusion in queries. > >>-- > >>Joe Brockmeier > >>j...@zonker.net > >>Twitter: @jzb > >>http://www.dissociatedpress.net/ > > > > > Jessica T. CloudStack Tech Pubs
