[Development] Branches and time based releases
Tuukka.Turunen at digia.com
Sat Mar 1 12:05:48 CET 2014
Intention is that users could easier than before move to new minor releases. With Qt 4.x it has sometimes been hard for users to migrate to newer ones. We are still quite early with Qt 5 to know if this works.
I fully agree that we should do more patch releases than we have done so far. Especially with Qt 5.1 having one more patch would have been great, but we had to skip it in favor of Qt 5.2 due to the introduction of mobile ports. And for Qt 5.2.1 the need is less since Qt 5.3 comes so soon.
I am quite sure Qt 5.3 will have more than one patch release.
> "Uwe Rathmann" <Uwe.Rathmann at tigertal.de> kirjoitti 25.2.2014 kello 10.02:
>> On Mon, 24 Feb 2014 21:11:47 +0000, Knoll Lars wrote:
>> So to sum it up, I believe the release model we currently have works
>> pretty well, certainly better than anything we have had in the past.
> Maybe I'm allowed to throw in the point of view of a user:
> last week we had the discussion about which version of Qt to use for a
> new project.
> What we have seen with Qt5 so far were 5.x.0 releases that were time -
> not quality - driven + only few maintenance releases ( 2 for 5.0, 1 for
> 5.1 and 5.2 ). In the past there have also been less stable versions of
> Qt, but more maintenance releases ( f.e 4 for 4.7 and 4.6 ) we could
> So our conclusion was that we have a regression in quality - exactly
> because of the time based releases - and to act very conservative with Qt
> version updates.
> Time based releases might be good for creating more versions in time, but
> what is it worth, when users don't follow anymore ?
> PS: our discussion ended with a decision for Qt 5.1 because of not
> trusting all the changes that happened under the hood of Qt 5.2
> Development mailing list
> Development at qt-project.org
More information about the Development