Timeline of releases
-
AFAIK, release dates for Qt are always "when it's done".
Recent conversations on Qt ML suggest that there are some bugs to be squished before 4.8 is out, and it would probably take a couple of weeks.
-
Yes, I noticed that too :-)
But I have a feeling that the Qt project is trying to improve. That would be in my opinion a huge step forward to keep us developers not in the darkness.
Each professional project is doing this, especially projects which are so big and vibrating.
-
[quote author="walteste" date="1322308081"]Yes, I found this too. Thank you!
I started this Thread as a suggestion for the Qt Project.
To whom we can address this?[/quote]The development mailing list perhaps? Although just as -Gerolf- Volker (sorry :)) stated, this 6 month schedule is already on.
What's so wrong about "when it's done" anyway? I do refer getting the content when it's ready and bug-free. Since the code is open, I can always use most current sources when I need to. Forcing it into a schedule can be a bit dangerous - ppl would rush to put in new features because a new version HAS to have new features, right? IMO, a stable code is as good now as it will be a month later, we don't need to give it a new number just because there is a release scheduled.
... just some random ramblings. Now I read this post again, I'm not so sure about it ;)
-
Well, I can see the point of wanting to have a release date. For instance, our company is planning to upgrade to Qt 4.8 when it is available. That does require work however (building and testing and running autotests for multiple platforms and configurations), so that work will need to be scheduled. Having a release date will make that easier. We do want to upgrade rather sooner than later, as that gives us more time in the actual development cycle to actually start using the new features.
-
I am definitely too young for this, then :) Coding is still only hobby for me, with no requirements "from above". You're right, of course, in these circumstances having the set date is clearly advantageous.
-
Yes, as mentioned by Andre, there are a lot of dependend works to schedule. It would make life much easier, if we would get at least an approximate ETA.
[quote author="Andre" date="1322313122"]Well, I can see the point of wanting to have a release date. For instance, our company is planning to upgrade to Qt 4.8 when it is available. That does require work however (building and testing and running autotests for multiple platforms and configurations), so that work will need to be scheduled. Having a release date will make that easier. We do want to upgrade rather sooner than later, as that gives us more time in the actual development cycle to actually start using the new features. [/quote]
-
At least, this is some good news :-)
What can be done to address the ETA discussion to the Qt Team?
[quote author="Andre" date="1322570404"]Last thing I heard (mind you: very unofficial, non-verified rumour-level information), is that a release is expected 1-3 weeks from now. [/quote]
-
[quote author="walteste" date="1322570771"]At least, this is some good news :-)
What can be done to address the ETA discussion to the Qt Team?
[/quote]Go ahead if you want to annoy the devs and cry for being ignored in the future...
This discussion has been done over and over in the last years, don't expect anything than "OMG - not again".
-
At the devdays, there was talk that for the Qt 5 series, a time-based release schedule is seriously considdered. I am not sure if it was decided on yet, though. I suggest you pop into the development mailinglist of qt-project, and discuss this issue there.
