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

Stable version as default in docs #478

Open
leonlan opened this issue Feb 19, 2024 · 8 comments
Open

Stable version as default in docs #478

leonlan opened this issue Feb 19, 2024 · 8 comments
Assignees
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@leonlan
Copy link
Member

leonlan commented Feb 19, 2024

Is your feature request related to a problem? Please describe

Most users install PyVRP through PyPI and so they use the stable version. However, www.pyvrp.org shows the documentation for the latest development version by default, possibly confusing users when they find features in the docs that aren't released yet.

Describe the solution you'd like

@leonlan leonlan added the documentation Improvements or additions to documentation label Feb 19, 2024
@N-Wouda
Copy link
Member

N-Wouda commented Feb 19, 2024

Related: #273 (but that issue covers a whole bunch of things).

@leonlan leonlan self-assigned this Mar 18, 2024
@leonlan
Copy link
Member Author

leonlan commented Mar 21, 2024

I'll pick this up ASAP. We're getting many questions about stuff not working because of this 😅

@N-Wouda
Copy link
Member

N-Wouda commented Mar 21, 2024

We also have the "older" docs hosted in this repository: https://github.com/PyVRP/PyVRP.github.io. Those are available at https://pyvrp.github.io/v0.7.0/, and so on. It'd be nice if we can somehow merge all that together so that:

  • pyvrp.org -> latest stable
  • pyvrp.org/dev -> latest build on main
  • pyvrp.org/v<version> -> docs associated with version <version>

I don't really know how to do this. I do know statsmodels has things set up exactly this way. Maybe we can borrow some of their setup for our own purposes?

@N-Wouda N-Wouda added this to the v0.9.0 milestone Mar 22, 2024
@N-Wouda
Copy link
Member

N-Wouda commented Mar 22, 2024

I'm assigning this for 0.9.0, since we really ought to solve this ASAP.

@leonlan
Copy link
Member Author

leonlan commented Mar 29, 2024

I'm looking into how statsmodels does it for the next hour and will make notes in this comment.

@N-Wouda N-Wouda mentioned this issue Mar 30, 2024
6 tasks
@N-Wouda N-Wouda assigned N-Wouda and unassigned leonlan Jun 24, 2024
@N-Wouda
Copy link
Member

N-Wouda commented Jun 25, 2024

Alright I had hoped to work on this today, but the devcontainer stuff took a little longer and now it's getting late. There's always tomorrow :).

@N-Wouda N-Wouda removed this from the v0.9.0 milestone Jun 26, 2024
@N-Wouda
Copy link
Member

N-Wouda commented Jun 26, 2024

I don't want this to block a release of 0.9.0, but I'll try to finish it in the coming week.

@N-Wouda N-Wouda added this to the v0.10.0 milestone Jun 26, 2024
@N-Wouda
Copy link
Member

N-Wouda commented Jul 3, 2024

Possibly interesting: https://github.com/jimporter/mike

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants