[
https://issues.apache.org/jira/browse/TINKERPOP-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202457#comment-16202457
]
ASF GitHub Bot commented on TINKERPOP-1786:
-------------------------------------------
Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/721
There are two aspects to CHANGELOG - (1) developer notes on what was done
and (2) JIRA tickets. You are really just responsible for (1) - it is typically
a more descriptive explanation of everything that was added/modified. It is
also usually more readable to a user, who may be perusing it (as opposed to the
sometimes terse JIRA ticket titles).
The JIRA tickets get added on release by the release manager, so you don't
really need to reference JIRA tickets at all in the CHANGELOG yourself. So to
fix up your PR you just need to remove the `Improvements` header and the JIRA
ticket below it.
As for your PR to master and 3.3.x, you don't have to adjust
CHANGELOG....just leave your entries on 3.2.x - we assume that any fixes to
3.2.x fold are inclusive to 3.3.x and make reference to that in the CHANGELOG
so that we don't duplicate the entries. Let me know if what I have written here
isn't clear for some reason.
> Recipe and missing manifest items for Spark on Yarn
> ---------------------------------------------------
>
> Key: TINKERPOP-1786
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1786
> Project: TinkerPop
> Issue Type: Improvement
> Components: hadoop
> Affects Versions: 3.3.0, 3.1.8, 3.2.6
> Environment: gremlin-console
> Reporter: Marc de Lignie
> Priority: Minor
> Fix For: 3.2.7, 3.3.1
>
>
> Thorough documentation for running OLAP queries on Spark on Yarn has been
> missing, keeping some users from getting the benefits of this nice feature of
> the Tinkerpop stack and resulting in a significant number of questions on the
> gremlin users list.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
