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

Update deprecation policy document for Qiskit 1.0 (backport #11775) #11813

Merged
merged 1 commit into from
Feb 15, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 15, 2024

This is an automatic backport of pull request #11775 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

* Update deprecation policy document for Qiskit 1.0

This updates `DEPRECATION.md` to bring it inline with the documentation
hosted on https://docs.quantum.ibm.com.  The policy described in this
commit is intended to match what we already agreed on and posted
publicly, but this particular file got slightly out-of-sync during the
initial deployment of the new hosted documentation and the split of
certain documentation content from this repository.

Most notably, this commit makes the exact extent of the public interface
much clearer.  We no longer use the "implicit based on object name"
form, but only commit to publicly documented objects being part of the
public interface.

* Commit to raising a warning on experimental features

* Remove comment on internal import policy

(cherry picked from commit be8bea1)
@mergify mergify bot requested a review from a team as a code owner February 15, 2024 14:58
@qiskit-bot
Copy link
Collaborator

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:

  • @Qiskit/terra-core

@github-actions github-actions bot added documentation Something is not clear or an error documentation Changelog: None Do not include in changelog labels Feb 15, 2024
@github-actions github-actions bot added this to the 1.0.0 milestone Feb 15, 2024
@coveralls
Copy link

Pull Request Test Coverage Report for Build 7917880432

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 8 unchanged lines in 1 file lost coverage.
  • Overall coverage increased (+0.01%) to 89.238%

Files with Coverage Reduction New Missed Lines %
crates/qasm2/src/lex.rs 8 91.94%
Totals Coverage Status
Change from base Build 7917668691: 0.01%
Covered Lines: 58866
Relevant Lines: 65965

💛 - Coveralls

@jakelishman jakelishman added this pull request to the merge queue Feb 15, 2024
Merged via the queue into stable/1.0 with commit b73d77d Feb 15, 2024
14 checks passed
@mergify mergify bot deleted the mergify/bp/stable/1.0/pr-11775 branch February 15, 2024 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Changelog: None Do not include in changelog documentation Something is not clear or an error documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants