[
https://issues.apache.org/jira/browse/TINKERPOP-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18142654#comment-18142654
]
ASF GitHub Bot commented on TINKERPOP-3303:
-------------------------------------------
Cole-Greer commented on code in PR #3768:
URL: https://github.com/apache/tinkerpop/pull/3768#discussion_r4532121371
##########
docs/src/dev/developer/release.asciidoc:
##########
@@ -291,8 +291,11 @@ the help of a PMC member for those steps.
... Consider direct deploy with `npm publish --otp <otp>` from
`gremlin-js/gremlin-javascript/` - if using this method, ensure the `npm`
version aligns with the one expected by the branch.
.. `mvn deploy -pl :gremlint -DskipTests -Dnpm`
... Consider direct deploy with `npm publish --otp <otp>` from
`gremlin-js/gremlint/` - if using this method, ensure the `npm` version aligns
with the one expected by the branch.
+.. `bin/process-docs.sh` to build the documentation for the tag, since the
`clean` above removed it. `gremlin-mcp`
Review Comment:
I'm not a big fan of the timing of the docs bundling (happening just prior
to npm publish). It would be nice if we could bundle the docs into mcp right
after they are built and deployed during vote thread prep. That way we wouldn't
need to rebuild docs on publication day, and we could included in the source
release and the release commit+tag.
I think this process is fine for now, just something I may want to revisit
after we've run it for a few releases.
> Serve docs from gremlin-mcp
> ---------------------------
>
> Key: TINKERPOP-3303
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3303
> Project: TinkerPop
> Issue Type: Improvement
> Components: mcp
> Affects Versions: 3.8.2
> Reporter: Stephen Mallette
> Assignee: Stephen Mallette
> Priority: Major
>
> Serve markdown forms of TinkerPop documentation from gremlin-mcp
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
