Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare 0.17.0 release #6075

Merged
merged 73 commits into from
Apr 1, 2021
Merged

Prepare 0.17.0 release #6075

merged 73 commits into from
Apr 1, 2021

Conversation

mtreinish
Copy link
Member

@mtreinish mtreinish commented Mar 24, 2021

Summary

To prepare for the upcoming 0.17.0 release this commit moves all the
release notes into a 0.17 subdirectory to keep them separate from future
development notes post-release. It also adds an incomplete release note
to add the prelude section providing the high level overview of the
release. When this merges it should be the commit used to tag the 0.17.0
release.

Details and comments

TODO:

  • Cleanup and fix release notes

@mtreinish mtreinish added the on hold Can not fix yet label Mar 24, 2021
@mtreinish mtreinish added this to the 0.17 milestone Mar 24, 2021
@mtreinish mtreinish requested a review from a team as a code owner March 24, 2021 11:23
To prepare for the upcoming 0.17.0 release this commit moves all the
release notes into a 0.17 subdirectory to keep them separate from future
development notes post-release. It also adds an incomplete release note
to add the prelude section providing the high level overview of the
release. When this merges it should be the commit used to tag the 0.17.0
release.
@mtreinish mtreinish removed the on hold Can not fix yet label Apr 1, 2021
@mtreinish mtreinish added the on hold Can not fix yet label Apr 1, 2021
@mtreinish mtreinish added automerge and removed on hold Can not fix yet labels Apr 1, 2021
deprecated) and provides the operators and state functions which are
used to build quantum algorithms. For details on migrating from
``qiskit-aqua`` to this new module please refer to the migration guide
"INSERT LINK HERE"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should fill this in

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is intentional and unfortunate side effect of our split documentation builds, see my comments starting here: #6075 (comment)

I will update this in the release notes post release.

@mergify mergify bot merged commit ce15f8a into Qiskit:master Apr 1, 2021
@mtreinish mtreinish deleted the prepare-0.17 branch April 1, 2021 15:34
Comment on lines +10 to +11
applying several individual pauli gates to different qubits at the
simultaneously. This is primarily useful for simulators which can use this
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
applying several individual pauli gates to different qubits at the
simultaneously. This is primarily useful for simulators which can use this
applying several individual pauli gates to different qubits
simultaneously. This is primarily useful for simulators which can use this

specified as an integer or another type which is castable to unambiguous
integers(e.g. ``2.0``). Non-integer values will now raise an error as the
intent in those cases was unclear (you can't have fractional bits). For
more, information on why this was changed refer to:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
more, information on why this was changed refer to:
more information on why this was changed refer to:

Comment on lines +6 to +9
:class:`qiskit.pulse.PulseChannel`. These classes are designed to be
parent classes for different user facing channel classes, such
as :class:`qiskit.pulse.DriveChannel`, and not something directly used.
When instantiated directly they were not actually usable. If you were
Copy link
Contributor

@lcapelluto lcapelluto Apr 1, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
:class:`qiskit.pulse.PulseChannel`. These classes are designed to be
parent classes for different user facing channel classes, such
as :class:`qiskit.pulse.DriveChannel`, and not something directly used.
When instantiated directly they were not actually usable. If you were
:class:`qiskit.pulse.PulseChannel`. These classes are designed to
classify types of different user facing channel classes, such
as :class:`qiskit.pulse.DriveChannel`, but do not have a definition
as a targeted resource. If you were

Comment on lines +10 to +11
previously directly instantiate either :class:`qiskit.pulse.Channel` or
:class:`qiskit.pulse.PulseChannel` this no longer works.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
previously directly instantiate either :class:`qiskit.pulse.Channel` or
:class:`qiskit.pulse.PulseChannel` this no longer works.
previously directly instantiating either :class:`qiskit.pulse.Channel` or
:class:`qiskit.pulse.PulseChannel`, this is no longer allowed. Please use
the appropriate subclass.

upgrade:
- |
It is now no longer possible to instantiate a base channel without
a prefix such as :class:`qiskit.pulse.Channel` or
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
a prefix such as :class:`qiskit.pulse.Channel` or
a prefix, such as :class:`qiskit.pulse.Channel` or

- |
A new kwarg, ``user_cost_dict`` has been added to the constructor for the
:class:`qiskit.transpiler.passes.TemplateOptimization` transpiler pass.
This enables users to providing a custom cost dictionary for the gates to
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This enables users to providing a custom cost dictionary for the gates to
This enables users to provide a custom cost dictionary for the gates to

ElePT pushed a commit to ElePT/qiskit that referenced this pull request Jun 27, 2023
* Prepare 0.17.0 release

To prepare for the upcoming 0.17.0 release this commit moves all the
release notes into a 0.17 subdirectory to keep them separate from future
development notes post-release. It also adds an incomplete release note
to add the prelude section providing the high level overview of the
release. When this merges it should be the commit used to tag the 0.17.0
release.

* Add feature note for aqua migrated modules

* Update release notes abd add piecewise chebyshev to docs and library export

* Update more release notes and add abstract pass classes to docs

* More release note updates

* Update more release notes and add clifford_decompose to api docs

* Add RZXCalibration pass and templates to docs and update release notes

* Update more release notes

* Fix typo in decompose_clifford imports and release notes

* Fix docs build

* Add hellinger_distance to docs

* Add RZXCalibrationBuilder to the docs

* More release note updates

* Fix import error

* Fix RZXCalibrationBuilder docstring

* Finish updating the new feature release notes

* Fix lint

* Apply suggestions from code review

Co-authored-by: Julien Gacon <gaconju@gmail.com>

* Move new release notes to 0.17 dir and update

* Fix RVGate docs and start updating upgrade notes

* Fix PauliGate example circuit visualization

* Fix typo

* More release note updates

* Update meas_map release note again

* Fix whitespace in meas_map release note

* Fix docs build

* Update almost all of the upgrade notes

* Add latex to docs job env

* Revert "Add latex to docs job env"

This reverts commit 8080cb5.

* Remove latex drawing from the release notes

Getting the texlive distribution with qcircuit installed in CI is
proving problematic in the interest of time and finishing the other
releasenotes instead of relying on it this just changes the latex drawer
jupyter execute to be a code block and not depend on being able to run
pdftlatex at docs build time.

* Remove fix note for unreleased feature

* Move and update new release notes

* Remove unnecessary upgrade note about internal API changes

* More release note updates

* More release note updates

* Even more release note updates

* Fix syntax error

* Fix docs build

* Move new release notes and fix docs issues from Qiskit#5609

* Update more release notes

* Move new release notes

* More release note updates

* Finish fixes notes

* Fix docs build

* Update more relaese notes

* Apply suggestions from code review

Co-authored-by: Naoki Kanazawa <nkanazawa1989@gmail.com>

* More note fixes

* Update new release notes

* Apply suggestions from code review

Co-authored-by: Kevin Krsulich <kevin@krsulich.net>

* Move and update new release notes

* Apply suggestions from code review

Co-authored-by: Kevin Krsulich <kevin@krsulich.net>

* cleaning up docs for vqe

* clean up extend

* Fix reno merge commit error

* Revert accidental tox.ini change

* Tweak release note wording

* Move and update new release notes

* Attempt to retrigger azure

Co-authored-by: Julien Gacon <gaconju@gmail.com>
Co-authored-by: Lauren Capelluto <laurencapelluto@gmail.com>
Co-authored-by: Naoki Kanazawa <nkanazawa1989@gmail.com>
Co-authored-by: Kevin Krsulich <kevin@krsulich.net>
Co-authored-by: Jay Gambetta <jay.gambetta@us.ibm.com>
ElePT pushed a commit to ElePT/qiskit-algorithms-test that referenced this pull request Jul 17, 2023
* Prepare 0.17.0 release

To prepare for the upcoming 0.17.0 release this commit moves all the
release notes into a 0.17 subdirectory to keep them separate from future
development notes post-release. It also adds an incomplete release note
to add the prelude section providing the high level overview of the
release. When this merges it should be the commit used to tag the 0.17.0
release.

* Add feature note for aqua migrated modules

* Update release notes abd add piecewise chebyshev to docs and library export

* Update more release notes and add abstract pass classes to docs

* More release note updates

* Update more release notes and add clifford_decompose to api docs

* Add RZXCalibration pass and templates to docs and update release notes

* Update more release notes

* Fix typo in decompose_clifford imports and release notes

* Fix docs build

* Add hellinger_distance to docs

* Add RZXCalibrationBuilder to the docs

* More release note updates

* Fix import error

* Fix RZXCalibrationBuilder docstring

* Finish updating the new feature release notes

* Fix lint

* Apply suggestions from code review

Co-authored-by: Julien Gacon <gaconju@gmail.com>

* Move new release notes to 0.17 dir and update

* Fix RVGate docs and start updating upgrade notes

* Fix PauliGate example circuit visualization

* Fix typo

* More release note updates

* Update meas_map release note again

* Fix whitespace in meas_map release note

* Fix docs build

* Update almost all of the upgrade notes

* Add latex to docs job env

* Revert "Add latex to docs job env"

This reverts commit 8080cb58ea0c0faad270197c61d2cececff8da1e.

* Remove latex drawing from the release notes

Getting the texlive distribution with qcircuit installed in CI is
proving problematic in the interest of time and finishing the other
releasenotes instead of relying on it this just changes the latex drawer
jupyter execute to be a code block and not depend on being able to run
pdftlatex at docs build time.

* Remove fix note for unreleased feature

* Move and update new release notes

* Remove unnecessary upgrade note about internal API changes

* More release note updates

* More release note updates

* Even more release note updates

* Fix syntax error

* Fix docs build

* Move new release notes and fix docs issues from Qiskit/qiskit#5609

* Update more release notes

* Move new release notes

* More release note updates

* Finish fixes notes

* Fix docs build

* Update more relaese notes

* Apply suggestions from code review

Co-authored-by: Naoki Kanazawa <nkanazawa1989@gmail.com>

* More note fixes

* Update new release notes

* Apply suggestions from code review

Co-authored-by: Kevin Krsulich <kevin@krsulich.net>

* Move and update new release notes

* Apply suggestions from code review

Co-authored-by: Kevin Krsulich <kevin@krsulich.net>

* cleaning up docs for vqe

* clean up extend

* Fix reno merge commit error

* Revert accidental tox.ini change

* Tweak release note wording

* Move and update new release notes

* Attempt to retrigger azure

Co-authored-by: Julien Gacon <gaconju@gmail.com>
Co-authored-by: Lauren Capelluto <laurencapelluto@gmail.com>
Co-authored-by: Naoki Kanazawa <nkanazawa1989@gmail.com>
Co-authored-by: Kevin Krsulich <kevin@krsulich.net>
Co-authored-by: Jay Gambetta <jay.gambetta@us.ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants