Prepare 1.3.0 release #13447
Prepare 1.3.0 release #13447
Conversation
raynelfss
added
on hold
|
One or more of the following people are relevant to this code:
|
releasenotes/notes/1.3/add-more-sabre-trials-9b421f05d2f48d18.yaml
Outdated
Show resolved
Hide resolved
releasenotes/notes/1.3/add-gates-to-collect-clifford-af88dd8f7a2a4bf9.yaml
Outdated
Show resolved
Hide resolved
releasenotes/notes/1.3/add-gates-to-collect-clifford-af88dd8f7a2a4bf9.yaml
Outdated
Show resolved
Hide resolved
releasenotes/notes/1.3/binary-arithmetic-gates-6cd2b1c8112febe0.yaml
Outdated
Show resolved
Hide resolved
raynelfss
force-pushed
the
prepare-1.3
branch
from
2c63b31
to
bdd938a
Compare
|
I have checked all release notes to the best of my abilities now. @beckykd feel free to further review these. I should be posting the prelude release note sometime tomorrow. |
raynelfss
added
the
ci: test wheels
releasenotes/notes/1.3/deprecate-pulse-package-07a621be1db7fa30.yaml
Outdated
Show resolved
Hide resolved
releasenotes/notes/1.3/deprecate-pulse-package-07a621be1db7fa30.yaml
Outdated
Show resolved
Hide resolved
releasenotes/notes/1.3/deprecate-pulse-package-07a621be1db7fa30.yaml
Outdated
Show resolved
Hide resolved
releasenotes/notes/1.3/deprecate-pulse-package-07a621be1db7fa30.yaml
Outdated
Show resolved
Hide resolved
releasenotes/notes/1.3/deprecate-pulse-package-07a621be1db7fa30.yaml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
I'm not sure what the term "inlined" means. Can you rephrase?
"inlined onto the base circuit"
There was a problem hiding this comment.
I believe it's just mentioning how it's realigning new instructions onto a base circuit. Maybe the word re-align works better?
There was a problem hiding this comment.
"Inline" is a compiler term
There was a problem hiding this comment.
But also I think that note is from some prior release?
raynelfss
force-pushed
the
prepare-1.3
branch
2 times, most recently
from
6dffa85
to
b1e08f8
Compare
There was a problem hiding this comment.
Thanks for doing this, I've done a quick first pass through the notes but I still need to read the rendered output in sphinx to see how the complete notes read. From this first pass though I have a few concerns before I feel this is ready to merge and subsequently tagging the release.
The first is there are some notes that are already published on prior releases we need to delete those files from the stable/1.3 branch in this PR to avoid duplicating them. You can just git rm these files, but please do an audit of all the notes in the rendered output to make sure none exist on https://docs.quantum.ibm.com/api/qiskit/release-notes/1.2 or https://docs.quantum.ibm.com/api/qiskit/release-notes/1.1
The second large concern is around how we're documenting performance improvements. We are very inconsistent about how we're reporting speedups across the board. A lot of synthesis functions are called out individually as having been ported to rust and citing a speedup factor. While for the transpiler passes only some do this, the basis translator stands out prominently as being one of the few that did this. If we're going to call these out as feature notes we should be consistent and ensure we do it for all of them. Or if we feel it's not important to document them individually as a long list it is probably better to consolidate the multiple notes into a single note for passes that lists out the passes we've ported to rust and they're generally faster. We should do the same thing for synthesis functions too. Personally I think a single large note documenting all of them is better for readers than doing a lot of small notes.
A smaller thing is I feel like many release notes were not checked over for completeness or correct categorization and we should ensure this is all correct before publishing the release notes.
| @@ -6,7 +6,7 @@ features_circuits: | |||
| See :ref:`circuit-real-time-methods` for more in-depth discussion on all of these. | |||
There was a problem hiding this comment.
This note file needs to be deleted it was already released in 1.1.0.
| Qiskit version 1.3.0 brings in major performance and quality improvements | ||
| for the transpiler. The minimum required Python version is now 3.9. |
There was a problem hiding this comment.
What are the quality improvements?
There was a problem hiding this comment.
With this, I was mainly referring to the refactoring of the circuit library and the many additions to the synthesis transpiler passes and plugins, all of which were aimed at better performance and quality of the transpiler. But I can change this if you believe it is not the best way of putting it.
| Qiskit version 1.3.0 brings in major performance and quality improvements | ||
| for the transpiler. The minimum required Python version is now 3.9. |
There was a problem hiding this comment.
I'd probably move this to the end since it's more just a secondary FYI and not a headline thing.
| * The deprecation of the Qiskit pulse module and all of its related components. | ||
| The pulse module and its functionality will be part of `Qiskit Dynamics <https://github.com/qiskit-community/qiskit-dynamics>`_. |
There was a problem hiding this comment.
Typically I wouldn't highlight this in the prelude. We have the full release notes and a dedicated deprecation section for this. The prelude is really just for the most important changes in the release and a deprecation normally doesn't fall into this in my opinion. The removal in 2.0 probably would though (although those release notes are going to be huge).
releasenotes/notes/1.3/backend-sampler-v2-level1-dc13af460cd38454.yaml
Outdated
Show resolved
Hide resolved
| in the run options, the results from the backend will be treated as level 1 | ||
| results rather as bit arrays (the level 2 format). | ||
| results instead of bit arrays (the level 2 format). | ||
| upgrade: |
There was a problem hiding this comment.
Is this really an upgrade note of a fix note? If it's an upgrade note we should explain the rationale behind the change, and also change the category to upgrade_primitives.
- Move loose release notes.
Co-authored-by: Rebecca Dimock <[email protected]>
Co-authored-by: Julien Gacon <[email protected]>
Co-authored-by: Rebecca Dimock <[email protected]> Co-authored-by: Julien Gacon <[email protected]> Co-authored-by: Elena Peña Tapia <[email protected]>
Co-authored-by: Rebecca Dimock <[email protected]>
Co-authored-by: Rebecca Dimock <[email protected]> Co-authored-by: Julien Gacon <[email protected]>
Co-authored-by: Rebecca Dimock <[email protected]>
Co-authored-by: Elena Peña Tapia <[email protected]>
Co-authored-by: Matthew Treinish <[email protected]>
Co-authored-by: Matthew Treinish <[email protected]>
Co-authored-by: Matthew Treinish <[email protected]>
raynelfss
force-pushed
the
prepare-1.3
branch
from
5669ca3
to
bbe57f2
Compare
releasenotes/notes/1.3/deprecate-basic-simulator-configuration-9d782925196993e9.yaml
Outdated
Show resolved
Hide resolved
…-9d782925196993e9.yaml
Summary
The following commits set the version number on
stable/1.3to1.3.0in preparation for the1.3.0final release.Details and comments
The following commits will:
1.3.0.releasenotes/notes/1.3/folder.cargodependencies.releasenotes/notes/1.3/.