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

Documentation needs to be updated to 1.6.1 #558

Closed
ethangreen-dev opened this issue Jun 25, 2021 · 3 comments
Closed

Documentation needs to be updated to 1.6.1 #558

ethangreen-dev opened this issue Jun 25, 2021 · 3 comments
Assignees
Labels
enhancement New feature or request ✔️​ Issue / PR has been resolved
Milestone

Comments

@ethangreen-dev
Copy link
Collaborator

Our documentation is currently pinned to release 1.2.0 as seen here. This needs to updated to the latest release.

@ethangreen-dev ethangreen-dev added the enhancement New feature or request label Jun 25, 2021
@ethangreen-dev ethangreen-dev added this to the 1.6.1 milestone Jun 25, 2021
@ethangreen-dev ethangreen-dev self-assigned this Jun 25, 2021
@ethangreen-dev ethangreen-dev changed the title Documentation needs to be updated to 1.6.0 Documentation needs to be updated to 1.6.1 Jun 25, 2021
@ethangreen-dev
Copy link
Collaborator Author

Since documentation depends on the contents of the docs directory in the main branch, we will need to update documentation prior to merging into main.

@ethangreen-dev
Copy link
Collaborator Author

We need to determine where the documentation will live. If we continue to use readthedocs.io as our host a readthedocs branch would be ideal. If we use Github Pages, then we need to push changes to gh-pages. This decision is highly dependent on whether we can get access to configure the webhook that powers gillespy2.readthedocs.io.

Due to the scope of this change #494 will be resolved alongside this issue.

@ethangreen-dev
Copy link
Collaborator Author

In addition -- if we change our documentation host then all references to previous sites will need to be updated.

@ethangreen-dev ethangreen-dev added the ✔️​ Issue / PR has been resolved label Jun 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ✔️​ Issue / PR has been resolved
Projects
None yet
Development

No branches or pull requests

1 participant