On 10/5/2010 7:55 AM, Rusty Lynch wrote:
Perhaps we can pull in mobility 1.2 a bit earlier then we would pull
in the tip of a project, but before the 1.1 has even been released?
Do we already have a significant body of additional backends in
existence today in the tip of master that the backend developers feel
is ready to be used?
If these new back-ends are not yet in place (or in place but not
usable) then I would ask that we hold off for a bit longer and for now
integrate the 1.1-beta.
well
for QtMobility 1.2 to be an option for MeeGo 1.2, it needs to be
released by the end of December. I assume the Nokia QtMobility guys are
committing to this.
But this means we need to get a beta version few weeks before that, and
an alpha a few weeks before that.
guess what.... it's pretty soon already.... so the period of instability
is going to be really really short, short enough for MeeGo to just wait
it out.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
