-
Notifications
You must be signed in to change notification settings - Fork 14
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
Get a perma-link to the most recent stable SMIRNOFF spec page #121
Comments
Would it be better to have it link to |
Some of those posts specifically refer to specific (now outdated) versions of the spec, so it would make sense to think about how we should link to specific snapshots in future. |
FYI, I've fixed #184 by linking to the final cc: #198 |
The stable branch now builds! See the link in the OP, and openff-toolkit issue #339 |
Awesome. So the URL would be https://open-forcefield-toolkit.readthedocs.io/en/stable/ or, since it's now the default, https://open-forcefield-toolkit.readthedocs.io/ |
Hmm, the proposed change would hard-code this link to the
0.3.0
toolkit release's SMIRNOFF spec page. This could be a problem because tomorrow we're cutting the0.4.0
toolkit release, which will make substantial changes to this page (and if we hand-correct that, we'll eventually make more changes requiring an update of this link in the future).RTD is supposed to have a
stable
branch which corresponds to the latest tagged release, but that's not building for us. I'll try to figure out what's up with that and get us a perma-link to an up-to-date SMIRNOFF spec page.I'm going to merge this PR, because an outdated link is marginally better than a completely broken one. But I'm making an Issue to tackle this in the future.
Originally posted by @j-wags in #120 (comment)
The text was updated successfully, but these errors were encountered: