On Saturday, 21 de May de 2011 08:25:16 Stephen Kelly wrote: > That's kind of interesting because 4.8 releases mean no new API, so we > can't add API and then port our apps to it, then port to Qt5 and the new > API that is there by then. That would take a 4.9 release. Is something like > that impossible?
Having a Qt 4.9 release is kind of hard in two accounts. First, any new API we
introduce there must be a strict subset of what's in 5.0. There mustn't be in
4.9 anything new that isn't in 5.0.
Second, the schedules. We'd very much like to get 5.0 out of the door, final
release, one year from now. Considering it takes 10-11 months to make a Qt 4.x
minor release and we still *haven't* done the 4.8 one, there is no room in the
schedule for a 4.9 release. Even if there were, forcing the fact that 4.9 API
must be in 5.0 too could derail the 5.0 schedule.
> I'm thinking in terms of 'How do we port to Qt5'? I'm wondering if it's
> possible to some extent to do the porting to new APIs at a different time,
> and as different work, to porting to Qt5. Porting to Qt4Support in Qt5
> allows that too of course, but there is risk that it will be too buggy for
> some time, making 'real/full/complete/the old stuff is obsolete' ports
> harder, and meaning new API bugs don't get found. I don't know if that's a
> major issue. I'm just thinking out loud.
It should hopefully be basically a recompile for 95% of the apps.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Opengov mailing list Opengov@qt-labs.org http://lists.qt-labs.org/listinfo/opengov
