summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLiang Qi <liang.qi@qt.io>2017-12-08 13:59:07 +0100
committerLiang Qi <liang.qi@qt.io>2017-12-08 13:59:07 +0100
commit98454fbc2a687a6440ae5e61070ebd6073e8016d (patch)
tree66ea28649b95b3004ad36d70490b8dbf796f780f
parentb0948ec06644dd88ba8ec660c1fb39c49a6d0e70 (diff)
parentc7d99464c65a5bde663a8ec4daf3d343d8e9b14b (diff)
Merge remote-tracking branch 'origin/5.10.0' into 5.10
-rw-r--r--dist/changes-5.10.02
-rw-r--r--dist/changes-5.9.325
2 files changed, 26 insertions, 1 deletions
diff --git a/dist/changes-5.10.0 b/dist/changes-5.10.0
index 20264d10..c92d3787 100644
--- a/dist/changes-5.10.0
+++ b/dist/changes-5.10.0
@@ -4,7 +4,7 @@ included in this distribution. The documentation is also available online:
http://doc.qt.io/qt-5/index.html
-The Qt version 5.10 series is binary compatible with the 5.10.x series.
+The Qt version 5.10 series is binary compatible with the 5.9.x series.
Applications compiled for 5.9 will continue to run with 5.10.
Some of the changes listed in this file include issue tracking numbers
diff --git a/dist/changes-5.9.3 b/dist/changes-5.9.3
new file mode 100644
index 00000000..b26411cb
--- /dev/null
+++ b/dist/changes-5.9.3
@@ -0,0 +1,25 @@
+Qt 5.9.3 is a bug-fix release. It maintains both forward and backward
+compatibility (source and binary) with Qt 5.9.0.
+
+For more details, refer to the online documentation included in this
+distribution. The documentation is also available online:
+
+http://doc.qt.io/qt-5/index.html
+
+The Qt version 5.9 series is binary compatible with the 5.8.x series.
+Applications compiled for 5.8 will continue to run with 5.9.
+
+Some of the changes listed in this file include issue tracking numbers
+corresponding to tasks in the Qt Bug Tracker:
+
+https://bugreports.qt.io/
+
+Each of these identifiers can be entered in the bug tracker to obtain more
+information about a particular change.
+
+****************************************************************************
+* Qt 5.9.3 Changes *
+****************************************************************************
+
+ - Added a note to the documentation that waitForReadyRead() and
+ waitForBytesWritten() never time out if the parameter msecs is -1.