Update release notes

Qiskit · Nov 28, 2023 · 968e52f · 968e52f
1 parent f5068cd
commit 968e52f
Show file tree

Hide file tree

Showing 4 changed files with 11 additions and 13 deletions.
diff --git a/releasenotes/notes/add-py312-support-7077426af34ac5da.yaml b/releasenotes/notes/add-py312-support-7077426af34ac5da.yaml
@@ -1,4 +1,5 @@
 ---
 features:
   - |
-    Added support for using Qiskit with Python 3.12.
+    Added support for using Qiskit with Python 3.12. As of this release Qiskit
+    supports running with Python versions 3.8, 3.9, 3.10, 3.11, and 3.12.
diff --git a/releasenotes/notes/fix-qreg-visualization-after-layout-42d3e643b923d8bc.yaml b/releasenotes/notes/fix-qreg-visualization-after-layout-42d3e643b923d8bc.yaml
@@ -1,8 +1,9 @@
 ---
 fixes:
   - |
-    Fixed a bug in :class:`~.SabreLayout` where it would fail to add the layout
-    register information to the property set. This affected circuit visualization, as
-    ``circuit.draw()`` after transpilation with certain optimization levels would show
-    the full ``Qubit[register]`` label rather than the expected register name
-    (e.g. ``q0``).
+    Fixed a bug in :class:`~.SabreLayout` where it would fail to add the register
+    information to the :class:`.Layout` object used for :attr:`.TranspileLayout.initial_layout`.
+    This affected circuit visualization with :meth:`.QuantumCircuit.draw` and :func:`.circuit_drawer`
+    after transpilation which would show a virtual qubit label of the form ``Qubit[QuantumRegister(6, 'q', 0)]``
+    rather than the expected virtual qubit label using the register name (e.g. ``q0``).
+    Fixed `#11038 <https://github.com/Qiskit/qiskit/issues/11038>`__
diff --git a/releasenotes/notes/fix-schedule-qpy-use-symengine-05ae1dfab73e3ff8.yaml b/releasenotes/notes/fix-schedule-qpy-use-symengine-05ae1dfab73e3ff8.yaml
@@ -3,4 +3,6 @@ fixes:
   - |
     Fixed an issue with :func:`.qpy.dump` which would cause the function to
     potentially ignore the value of ``use_symengine`` when serializing a
-    :class:`.ScheduleBlock` object.
+    :class:`.ScheduleBlock` object. This would result in an invalid QPY
+    payload being generated as it would report it was using symengine for
+    symbolic expressions but actually contain sympy serialized data.
diff --git a/releasenotes/notes/fix_sim_backend-f3971b1ed4d0c4e6.yaml b/releasenotes/notes/fix_sim_backend-f3971b1ed4d0c4e6.yaml