[Development] Focusing bug fixes to 5.9 branch and patch releases during H1/17

Stottlemyer, Brett (B.S.) bstottle at ford.com
Tue Apr 11 15:09:34 CEST 2017

> On 4/11/17, 7:36 AM, "Development on behalf of Tuukka Turunen" <tuukka.turunen at qt.io> wrote:
> every fix that would have been part of 5.8.1 and more – a lot more. 

The reason for pushing to the 5.8 branch is because it *is* stable.  And since it has "... a lot more", the 5.9 branch is not stable.  Whether The Qt Company will generate any packaged versions on the 5.8 branch after the 5.8.0 release is really not the point, is it?

For those that are building from source and who have requirements for stability vs. new features, doesn't there need to be a stable HEAD to push to?  If the 5.8 branch is closed, those developers will be forced to move to 5.9 beta, or be required to find, cherry-pick and validate commits onto 5.8 themselves, right?  Leaving the branch open, with CI runs on changes, seems like the only way to keep a known stable HEAD available until the known stable HEAD is on the 5.9 branch.


More information about the Development mailing list