Add release note for namespace migration #1593
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In the recently merged Qiskit#1526 we moved the qiskit-aer package to move it's python namespace from qiskit.providers.aer to qiskit_aer. However, in that PR a release note was missing. This commit adds the missing release note to document the upgrade implications about the change. We should also mention this in the release notes prelude section, but that will occur in the release PR.
jakelishman
reviewed
Sep 2, 2022
Co-authored-by: Jake Lishman <jake@binhbar.com>
jakelishman
approved these changes
Sep 2, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
In the recently merged #1526 we moved the qiskit-aer package to move
it's python namespace from qiskit.providers.aer to qiskit_aer. However,
in that PR a release note was missing. This commit adds the missing
release note to document the upgrade implications about the change. We
should also mention this in the release notes prelude section, but that
will occur in the release PR.
Details and comments