On Tue, 2010-10-05 at 09:18 +0100, [email protected] wrote: > >Perhaps host a sandbox for the cutting edge > >mobility-1.2-hasn't-hit-tp-yet for those that really need it? > > In principle I kind of agree with Rusty but the practical implications > may ruin this. The Mobility 1.2/master branch is going to be open > battleground and regressions are to be expected. Where I see the > problem is on the backend side of things. A lot of our Mobility API's > will only get their Meego backend during the Mobility 1.2 development > phase. Hence a push of 1.1 libraries may bring the API to Meego but > the backend may not exist yet.
Are the new 1.1 APIs considered preliminary until the MeeGo backend also exists *and* there was time to write some real code using the APIs? IMHO it does not make sense to finalize on an API without implementing the backend. For MeeGo, I don't see that as desirable, in particular in a core component like Qt Mobility which is meant to be *the* MeeGo application API. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
