[
https://issues.apache.org/jira/browse/TINKERPOP-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408178#comment-17408178
]
Stephen Mallette commented on TINKERPOP-2591:
---------------------------------------------
The 3.5-dev branch had to be rebuilt after some problems with the branch
structure:
https://lists.apache.org/thread.html/r592cc8abb00729908047d92d8a55e9f980ec1d953d3073b88b2858c3%40%3Cdev.tinkerpop.apache.org%3E
The following commits related to this issue were cherry-picked to 3.5-dev and
then merged to master with {{--strategy=ours}}
ecac064656eb0c321bcfbb42a92d5e2544cc746f
> Administrative adjustments to gremlint site
> -------------------------------------------
>
> Key: TINKERPOP-2591
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2591
> Project: TinkerPop
> Issue Type: Improvement
> Components: gremlint
> Affects Versions: 3.5.1
> Reporter: Stephen Mallette
> Assignee: Øyvind Sæbø
> Priority: Minor
> Fix For: 3.6.0, 3.5.2
>
>
> I presume that we can now pin the gremlint web site to a particular version
> of the gremlint library?
> https://github.com/apache/tinkerpop/blob/e1b377a98b97578017d8d815daed76e11b04c9f7/docs/gremlint/package.json#L14
> I guess we'd want the version to match the current version of the library?
> 3.5.2-alpha1 for the case of 3.5.2-SNAPSHOT? and then when we do
> {{bin/generate-home.sh}} we could swap that automatically to whatever the
> most recent version is published to npm? or i guess just setting it to ^3.5.1
> will capture the latest in npm and the local alphas?
> I think it would be good if the gremlint web site had the version displayed
> in a footer along with the standard "Copyright © 2015-2021 The Apache
> Software Foundation." and perhaps a link back to the
> https?tinkerpop.apache.org site.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
