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

Migrate to Qiskit 1.0 #2

Open
frankharkins opened this issue Apr 11, 2024 · 3 comments
Open

Migrate to Qiskit 1.0 #2

frankharkins opened this issue Apr 11, 2024 · 3 comments

Comments

@frankharkins
Copy link

frankharkins commented Apr 11, 2024

I'm making this issue because this project is part of the Qiskit ecosystem.

As of June 2024, we're introducing a requirement that all projects are compatible with Qiskit 1.0. New users will be using Qiskit 1.0 and we want to make sure any projects we guide them to work straight away.

See our migration guide and let me know if you need any support (such as answering questions about Qiskit or code review). With Qiskit's new stability policy, this should be the last change needed for a while.

In June, we will test out your project and remove it if it doesn't work with Qiskit 1.0. This includes cases in which we can't get the project working because the documentation is lacking. We do value your project so let me know if you need any help migrating or have any other concerns.

@atlytle
Copy link
Owner

atlytle commented Apr 28, 2024

Thanks for the heads up, @frankharkins. The main functionality should be 1.0 compliant, but I may need to make some changes to pass CI tests. Is it ok if I reach out on Slack or email about this in the coming month? Thanks a lot for your help!

@frankharkins
Copy link
Author

Is it ok if I reach out on Slack or email about this in the coming month?

Absolutely!

@atlytle
Copy link
Owner

atlytle commented May 30, 2024

I've updated the repo, removing references to Opflow and updating requirements. I updated the README to reflect the changes and document current usage. Could you let me know if there's anything else that jumps out as needing changed for the ecosystem? Thanks for your help with this, @frankharkins.

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

No branches or pull requests

2 participants