> > 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.
Afaik, we're supposed to deliver Qt Mobility 1.2 for MeeGo 1.2. Now, if the timeframe doesn't map, I won't push QtMobility 1.2 to Trunk:Testing but 1.1 beta2 instead. We'll see later if QtMobility 1.2 is an option or definitely not. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
