[Releasing] HEADS-UP: Branching from 'dev' to '5.9' started

Jason H jhihn at gmx.com
Mon Jan 30 16:15:26 CET 2017

That's great, but I'm a commercial license owner. Both of these are relatively minor changes that mean a lot to me.

Paring my list down to just API changes, I have these two:
https://bugreports.qt.io/browse/QTBUG-51133 <- this is the main one I'm talking about (Feb 2016)
https://bugreports.qt.io/browse/QTBUG-52013 (Mar 2016)

> Sent: Saturday, January 28, 2017 at 1:31 PM
> From: "Thiago Macieira" <thiago.macieira at intel.com>
> To: releasing at qt-project.org
> Subject: Re: [Releasing] HEADS-UP: Branching from 'dev' to '5.9' started
> On sábado, 28 de janeiro de 2017 12:46:07 PST Jason H wrote:
> > The furious pace of major releases coupled with the API lock down is one of
> > my biggest compliants about Qt. Very simply if it isn't a bug fix, I'm
> > going to be waiting at least 12 months before the feature lands.
> > 
> > There has got to be a better way.
> What do you mean by 12 months? If someone adds finishes a feature by Monday, it 
> will be in the April release. That's 3 months.
> If they finish the feature on Friday, it'll be in the October/November release. 
> That's the longest possible case and that's 9 or 10 months.
> Now, reviewing features takes time. If you want it to get in the next release, 
> start early.

More information about the Releasing mailing list