On 10/5/2010 8:53 AM, Thiago Macieira wrote:
Em Terça-feira 05 Outubro 2010, às 17:21:30, Arjan van de Ven escreveu:
I think the Mobility 1.2 release is January, not December.
then it's not going to make MeeGo 1.2, and will make MeeGo 1.3 instead....
Feature freeze in December means what it means; all fundamental, core
libraries and components need to be released at that point.
And QtMobility certainly is such a core fundamental library.
Released in final versions at feature freeze? Would a beta or RC suffice for
feature freeze of core components?
I don't think it's realistic to already plan to be late... if a
realistic schedule slips a week or two, well sh** happens.
But if at the plan level it doesn't line up, that's not going to work.
What are the options to pull in the QtMobility 1.2 schedule ?
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
