Skip to content
This repository has been archived by the owner on Aug 19, 2023. It is now read-only.

Redirect aer docs to new import path #1596

Merged
merged 3 commits into from
Sep 15, 2022

Conversation

mtreinish
Copy link
Member

Summary

As part of the upcoming aer 0.11.0 release the project is moving to a
separate package/namespace and will no longer be part of qiskit.*.
This means the old documentation pages that existed for aer will no
longer be built because autodoc for the path will no longer be from
qiskit.providers.aer. To address this in the next metapackage release
this commit adds redirects from the existing aer documentation pages to
the new aer documentation.

Details and comments

Related to #1508

As part of the upcoming aer 0.11.0 release the project is moving to a
separate package/namespace and will no longer be part of `qiskit.*`.
This means the old documentation pages that existed for aer will no
longer be built because autodoc for the path will no longer be from
qiskit.providers.aer. To address this in the next metapackage release
this commit adds redirects from the existing aer documentation pages to
the new aer documentation.

Related to Qiskit#1508
@mtreinish mtreinish added the on hold Can not fix yet label Aug 31, 2022
@mtreinish
Copy link
Member Author

This is on hold until after aer 0.11.0 releases so the redirects have something to go to

To ease the migration of docs around the aer release this commit shifts
the redirect from the old import path to the new import path in the same
docs tree. This is needed for two reasons, while aer is still part of the
metapackage we should document it as such, and secondly the current state
of the Aer documentation isn't really for standalone hosting the docs
aren't really sufficient on their own yet. So until both situations are
resolved we should keep aer as part of the metapackage docs.
@mtreinish mtreinish changed the title Redirect aer docs to standalone aer page Redirect aer docs to new import path Sep 1, 2022
@mtreinish
Copy link
Member Author

I've updated this PR to keep aer as part of the metapackage, I explained the rationale in: Qiskit/qiskit@ac3169f for aer 0.12.0 we'll work on getting the standalone documentation in aer up to expectations. Then when aer isn't part of the metapackage anymore we'll be in a good place for updating the redirect to the standalone build

Copy link
Member

@jakelishman jakelishman left a comment

Choose a reason for hiding this comment

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

In principle this looks fine to me for once Aer 0.11 releases and is bumped into the metapackage.

@mtreinish mtreinish removed the on hold Can not fix yet label Sep 14, 2022
@jakelishman jakelishman merged commit 744fcbf into Qiskit:master Sep 15, 2022
@mtreinish mtreinish deleted the add-aer-redirects branch September 16, 2022 16:42
mtreinish added a commit to mtreinish/qiskit that referenced this pull request Sep 16, 2022
In Qiskit#1596 we added redirects from the old qiskit aer module paths to the
new `qiskit_aer` path. However, that PR added the redirects relative to
the root of the docs build and the sphinx-reredirects module does the
redirects relative to the dir of the source path. This is causing the
destination of the redirects to go to the wrong URL resulting in a 404.
This commit updates the redirect configuration to ensure that the
destination path is correct by treating the destination path relative to
the source path which fixes the broken redirects.
mergify bot pushed a commit that referenced this pull request Sep 16, 2022
In #1596 we added redirects from the old qiskit aer module paths to the
new `qiskit_aer` path. However, that PR added the redirects relative to
the root of the docs build and the sphinx-reredirects module does the
redirects relative to the dir of the source path. This is causing the
destination of the redirects to go to the wrong URL resulting in a 404.
This commit updates the redirect configuration to ensure that the
destination path is correct by treating the destination path relative to
the source path which fixes the broken redirects.
jakelishman pushed a commit to jakelishman/qiskit-terra that referenced this pull request Aug 11, 2023
* Redirect aer docs to standalone aer page

As part of the upcoming aer 0.11.0 release the project is moving to a
separate package/namespace and will no longer be part of `qiskit.*`.
This means the old documentation pages that existed for aer will no
longer be built because autodoc for the path will no longer be from
qiskit.providers.aer. To address this in the next metapackage release
this commit adds redirects from the existing aer documentation pages to
the new aer documentation.

Related to Qiskit/qiskit-metapackage#1508

* Switch to redirect in docs tree

To ease the migration of docs around the aer release this commit shifts
the redirect from the old import path to the new import path in the same
docs tree. This is needed for two reasons, while aer is still part of the
metapackage we should document it as such, and secondly the current state
of the Aer documentation isn't really for standalone hosting the docs
aren't really sufficient on their own yet. So until both situations are
resolved we should keep aer as part of the metapackage docs.
jakelishman pushed a commit to jakelishman/qiskit-terra that referenced this pull request Aug 11, 2023
)

In Qiskit/qiskit-metapackage#1596 we added redirects from the old qiskit aer module paths to the
new `qiskit_aer` path. However, that PR added the redirects relative to
the root of the docs build and the sphinx-reredirects module does the
redirects relative to the dir of the source path. This is causing the
destination of the redirects to go to the wrong URL resulting in a 404.
This commit updates the redirect configuration to ensure that the
destination path is correct by treating the destination path relative to
the source path which fixes the broken redirects.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants