[Development] New Qt5.3.1 snapshot available
Hi all, New Qt5.3.1 snapshot available here: http://download.qt-project.org/snapshots/qt/5.3/5.3.1/2014-06-19_117/ These packages are really close to final Qt 5.3.1 packages, only few changes are missing (see https://codereview.qt-project.org/#/c/87807/, patch set 2). https://codereview.qt-project.org/#/c/87807/ is under integration new packaging round will be started immediately when it succeed. Snapshot with that final content should be available in http://download.qt-project.org/snapshots/qt/5.3/5.3.1/ late today / tomorrow morning. These packages will be then Qt5.3.1 final candidate packages. Plan is to release Qt5.3.1 during next week we won't update these packages anymore if there isn't something really critical broken... Please test these packages inform us immediately if you find some really critical regression compared to Qt5.3.0 release. Br, Jani Qt5 changes in this snapshot: https://codereview.qt-project.org/#/c/87532/ : * qtbase 9c80a3b...c92ece4 (9): QRasterPlatformPixmap::createPixmapForImage(): Avoid crash when QImage conversion failes xcb: touch device mode is either Dependent or Direct, not Rel or Abs install .lib files for static libs again Flush xcb connection before EventDispatcher is going to block Fix data race in accessing QDBusConnectionPrivate::serviceNames Android: REG: Fix crash. Merge remote-tracking branch 'origin/stable' into 5.3 QFontComboBox sometimes became too wide because of wrong fixed size Android: Report something sensible for screen geometry * qtconnectivity 5fe214b...ad0df0d (1): Properly deal with pairing errors in btfiletransfer example * qtdeclarative 17ee404...1e39eb5 (3): Separate renderer out in OpenGL under QML example. Use newest QtQuick in rssnews demo Merge remote-tracking branch 'origin/stable' into 5.3 * qtmultimedia 150ff66...34ab2b5 (1): Improved audiooutput and audioinput examples. * qtquickcontrols f6845c2...d67c98c (1): Merge remote-tracking branch 'origin/stable' into 5.3 * qtserialport 450f79d...065f526 (1): Fix mixed up vendor and product identifiers * qttools 788638b...7017fe8 (1): Merge remote-tracking branch 'origin/stable' into 5.3 * qtwebkit f7d9266...ba4102c (1): Fix letter-spacing in SVG ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt5.3.1 known isssue
Hi all, Qt5.3.1 release is coming soon, please update known issues in http://qt-project.org/wiki/Qt531-KnownIssues Br, jani ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QtCS2014 - Expiring bug reports
Am 18.06.2014 11:09, schrieb Oswald Buddenhagen: On Tue, Jun 17, 2014 at 06:31:45PM +0200, Robert Löhning wrote: By the way: What will happen to bug reports from now closed identities? i'm inclined to change the reporters (and assignees) to the new accounts. it isn't exactly rocket science, only a bit of work... This sounds great! ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Windows QtCS Session, MSVC compiler versions
Hi, here are the notes from the Windows session: https://qt-project.org/groups/qt-contributors-summit-2014/wiki/Qs2014Windows We had a bit of discussion around whether to update the compilers during the lifetime of a minor release. This is relevant for 5.3 since it is planned to be supported for a longer time. For example, for MSVC-2013, options are: - Stick with the RTM / original version of MSVC-2013 for the lifetime of 5.3 since 5.3.0 was shipped with it - Update now to MSVC-2013 Update 2 and leave it as is for the lifetime of 5.3 - Keep updating continuously There are pros and cons for all options. With MSVC, it has happened that the runtime was changed by service packs in incompatible ways causing breakage. On the other hand, sticking to one version means that at some point it no longer matches what everyone else out there is using. What do you think? Regards, Friedemann -- Friedemann Kleint Digia, Qt ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Releasing] 5.3 branch temporarily closed
On Mon, Jun 16, 2014 at 12:50:41PM +, Heikkinen Jani wrote: Hi all, '5.3' branch ( 'stable' as well) is now temporarily closed because we are branching '5.3.1' from it. We are waiting all existing integrations to finish(either succeed or failed) merging from 'stable' to '5.3' once again before creating the '5.3.1' branch. From now on all changes targeted to Qt5.3.1 needs to be pushed to '5.3.1' branch (there shouldn't be many because most of blockers are already fixed). I will inform you when '5.3.1' branch is available when '5.3' branch is opened for changes to Qt5.3.2 5.3 is now open again. changes for stable can be staged, too, but you can't push updates any more - anything that is not (going to be) approved in the current incarnation needs to move to 5.3 (if enough people want such a service, i may open a short window for further updates to stable, but keeping it permanently open is no option). Br, Jani ___ Releasing mailing list releas...@qt-project.org http://lists.qt-project.org/mailman/listinfo/releasing ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
