Re: [Development] Using Native web view on OS X
Kai Koehne wrote: > Indeed, and we agreed to solve this properly by introducing a plugin based > architecture: https://codereview.qt-project.org/#/c/207651/ This wouldn't also be of interest for developers who want to target Apple's App Store. Assuming QtWebView is an appropriate choice for implementing a rich-text viewer for (mostly) local documents in any case. QtWebEngine is usually severely overkill for that purpose, QTextBrowser usually (just) not good enough. > > > It's just not something you want to do in a patch level release, because > stability. I'm thinking that stability shouldn't depend on whether you introduce this in a patchlevel release or a major release. (Or maybe I have a certain experience that "older" patch level releases are more stable? :) ) ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Branching from '5.10' to '5.10.1' started
Hi all, We have soft branched '5.10.1' from '5.10' on Friday. Target is to do final downmerge from '5.10' -> '5.10.1' Friday 2.2.2018. Please finalize ongoing changes in '5.10' and start using '5.10.1' for new changes. First Qt 5.10.1 snapshot is already under testing and we are targeting to get Qt 5.10.1 out as soon as possible after final downmerge. So please minimize changes for Qt 5.10.1 from now on to get it out quickly! br, Jani ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt branches & proposal how to continue with those
Hi, We have currently really many branches open: - 5.6 - 5.9 - 5.10 - 5.10.1 - 5.11 - dev In my opinion this is too much to handle effectively, especially because there is many branches in stable mode (see http://code.qt.io/cgit/meta/quips.git/tree/quip-0005.rst). Currently '5.6' is in 'strict' mode and '5.9', 5.10' & '5.11' are in stable... I think we need to change that to be able to work efficiently & get releases out. So I am proposing following changes starting from 1st Feb 2018: - '5.6' will move in 'very strict' mode - '5.9' will move in 'strict' mode. So no direct submissions anymore, just cherry picks from stable - '5.10' will be closed and Qt 5.10.1 will be the final release from Qt 5.10 series (5.6 and 5.9 are LTS branches so we shouldn't keep Qt 5.10 active too long) - '5.11' will be to one and only stable branch br, Jani ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt branches & proposal how to continue with those
On 29 January 2018 at 08:59, Jani Heikkinen wrote: > - '5.6' will move in 'very strict' mode > - '5.9' will move in 'strict' mode. So no direct submissions anymore, just > cherry picks from stable > - '5.10' will be closed and Qt 5.10.1 will be the final release from Qt 5.10 > series (5.6 and 5.9 are LTS branches so we shouldn't keep Qt 5.10 active too > long) > - '5.11' will be to one and only stable branch The problem here is that there are bugfixes that need to go into 5.9 but cannot go into 5.11, for a variety of reasons. We need to keep 5.9 open for direct submissions. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
