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?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
