Thiago Macieira wrote: > 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.
Why is that? Because Qt4Support or whatever will have to have all features of 4.x? > > 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 would see Qt 4.9 as something that could come after Qt5.0.0, but I was assuming that 4.x doesn't have to be a strict subset. I know nothing about kernels, but I think the linux 2.4 series is still maintained (I don't know if it gets features) even though 2.6 is quite mature now. I can see division of development and marketting attention and release effort being roadblocks for further Qt4 releases. Thanks, Steve. _______________________________________________ Opengov mailing list Opengov@qt-labs.org http://lists.qt-labs.org/listinfo/opengov
