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

Execution mode migration needs more context #2610

Open
1 of 5 tasks
jyu00 opened this issue Jan 30, 2025 · 2 comments
Open
1 of 5 tasks

Execution mode migration needs more context #2610

jyu00 opened this issue Jan 30, 2025 · 2 comments
Assignees
Labels
content 📄 needs triage 🤔 this issue needs to be prioritized by the docs team

Comments

@jyu00
Copy link
Collaborator

jyu00 commented Jan 30, 2025

URL to the relevant documentation

https://docs.quantum.ibm.com/migration-guides/sessions

Select all that apply

  • typo
  • code bug
  • out-of-date content
  • broken link
  • other

Describe the fix.

This page is titled Execution modes changes... but it doesn't say change from what. People might think we have yet another change in execution modes since they were released in April last year.

The page content also only talks about what the execution modes are and nothing about any migration actions.

@jyu00 jyu00 added content 📄 needs triage 🤔 this issue needs to be prioritized by the docs team labels Jan 30, 2025
@javabster
Copy link
Collaborator

Now that you mention it, do you think we still need this migration guide at all or could we remove it? it doesn't really read like a migration guide and it looks like all the info is already covered by the other execution modes guides. I'd argue we could just remove this

@jyu00
Copy link
Collaborator Author

jyu00 commented Feb 6, 2025

I agree we can just remove it. We sunset the old Session/Batch when the new execution modes were released back in April. So anyone using the old should have migrated to the new by now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content 📄 needs triage 🤔 this issue needs to be prioritized by the docs team
Projects
Status: No status
Development

No branches or pull requests

4 participants