[
https://issues.apache.org/jira/browse/TINKERPOP-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298937#comment-15298937
]
ASF GitHub Bot commented on TINKERPOP-1003:
-------------------------------------------
Github user spmallette commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/317#issuecomment-221404811
weird - i never noticed that you replied to my post in jira @lewismc - i'll
just say that i basically agree with what you wrote there. we can push off the
SEO stuff to another ticket. i'm fine with that. i guess what i'm still
concerned about here is the situation where someone does a `publish-docs.sh`
for 3.2.1-SNAPSHOT, and then someone else turns around and does one for
3.1.3-SNAPSHOT. In that case, what's in "current" is just constantly being
shifted around. I also don't think we we want to promote a SNAPSHOT as
"current'. We should make "current" our most recent production release that we
primarily promote on the web site - so our "current", if we did this today
would be a copy of 3.2.0-incubating.
I think that there should be something in the script that doesn't bother to
update "current" if the version is SNAPSHOT. I don't know what we do about the
actual release versions to prevent 3.1.6 from one day overwriting 3.3.0. See
the problem? any thoughts?
> Setting up latest/current links for bins and docs.
> --------------------------------------------------
>
> Key: TINKERPOP-1003
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1003
> Project: TinkerPop
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 3.1.0-incubating
> Reporter: Dylan Millikin
> Priority: Minor
>
> It would be good to have {{/latest}} URLs for doc and bins. As well as
> getting old docs dereferenced from search engins
> More info can be found in this thread:
> https://pony-poc.apache.org/thread.html/Zv6yx0dr64pliar
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
