Foward port release note updates for 0.22.0 release #8901
Merged
Conversation
This file contains 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
As part of the 0.22.0 release process we updated the release notes on the stable branch alone with bumping the version string for the package. This commit forward ports those changes from the stable branch to main. This will make it easier for us to backport any subsequent changes to the release notes as part of a potential 0.22.1 release.
|
Thank you for opening a new pull request. Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone. One or more of the the following people are requested to review this:
|
|
if I did this correctly the |
Pull Request Test Coverage Report for Build 3249381956
💛 - Coveralls |
jakelishman
approved these changes
Oct 14, 2022
mtreinish
added a commit
to mtreinish/qiskit-core
that referenced
this pull request
Jan 23, 2023
This commit prepares the 0.23.0 release, this involves 2 steps first changing all the version numbers to 0.23.0 from 0.23.0rc1 and secondly updating the release notes to prepare them for publishing. One key thing to note is that this PR removes the 0.22.0 release notes. This is because for the 0.22.0rc1 tag we neglected to move the release notes to a separate directory. So when we did that for the 0.22.0 final release we had to forward port this back to main so that any backports to stable/0.22 would be backportable (see Qiskit#8901). However, this causes reno to detect all the 0.22 release notes are incorrectly as part of the 0.23.0 development series. To fix this the simplest path forward was to remove the 0.22.0 release notes from the 0.23.0 branch (as in this PR).
mergify bot
pushed a commit
that referenced
this pull request
Jan 26, 2023
* Prepare 0.23.0 release This commit prepares the 0.23.0 release, this involves 2 steps first changing all the version numbers to 0.23.0 from 0.23.0rc1 and secondly updating the release notes to prepare them for publishing. One key thing to note is that this PR removes the 0.22.0 release notes. This is because for the 0.22.0rc1 tag we neglected to move the release notes to a separate directory. So when we did that for the 0.22.0 final release we had to forward port this back to main so that any backports to stable/0.22 would be backportable (see #8901). However, this causes reno to detect all the 0.22 release notes are incorrectly as part of the 0.23.0 development series. To fix this the simplest path forward was to remove the 0.22.0 release notes from the 0.23.0 branch (as in this PR). * Remove backported PRs * Start editting release note * More updates * Apply suggestions from code review Co-authored-by: Julien Gacon <gaconju@gmail.com> * Fix docs build errors * More udpates * Update more release notes One release note to call out is the release note for #8568 has been changed significantly. This is based on #9445 which is reverting some breaking changes made as part of #8568. * More updates * Finish feature note first pass * Start upgrade notes * Move and update new release notes * Fix docs build error * Finish first pass at upgrade notes * Finish first pass at deprecation notes * Finish first pass over release notes * Fix import cycle from dagcircuit * Apply suggestions from code review Co-authored-by: Kevin Hartman <kevin@hart.mn> * Apply suggestions from code review Co-authored-by: Jake Lishman <jake@binhbar.com> * Update releasenotes/notes/0.23/prepare-0.23.0-release-0d954c91143cf9a4.yaml * Fix analysis class definition in vf2 release note Co-authored-by: Julien Gacon <gaconju@gmail.com> Co-authored-by: Kevin Hartman <kevin@hart.mn> Co-authored-by: Jake Lishman <jake@binhbar.com>
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
As part of the 0.22.0 release process we updated the release notes on the stable branch alone with bumping the version string for the package. This commit forward ports those changes from the stable branch to main. This will make it easier for us to backport any subsequent changes to the release notes as part of a potential 0.22.1 release.
Details and comments