Or actually new feature requests go to 'unspecified' first and then the product manager decides on the release?
Really good points everyone so far, and it seems a lot of confusion comes from the fact using Bugzilla as the "featurezilla" :) AFAIK there was a plan to have a separate "landing page" for Features, I think that would go a long way helping this. One thing I am slightly confused.. I've understood MeeGo is about "contribution is king" ie. whoever is making a new feature (request) will have to have at least an idea on where the actual contribution (code in most cases) is coming from, if not the whole contribution. Isn't that the case? If so, how will potential interested contributors know what are key things missing from eg. a specific release? Jukka > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of ext Arjan van de Ven > Sent: 3. tammikuuta 2011 20:33 > To: Dave Neary > Cc: [email protected]; Pienimaki Sami (Nokia-MS/Tampere); Lavonius > Ville (Nokia-MS/Helsinki) > Subject: Re: [MeeGo-dev] MeeGo 1.2 Roadmap? > > On 1/3/2011 10:10 AM, Dave Neary wrote: > > just as a side note... > since we're about two or so weeks away from feature freeze for 1.2.... > it should be assumed that all feature requests that get filed are for > 1.3 ( in fact, that should have been the case from the day that 1.2 > development started, back in late October) > > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
