[
https://issues.apache.org/jira/browse/HIVE-16760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028748#comment-16028748
]
Thejas M Nair commented on HIVE-16760:
--------------------------------------
Yes, it makes sense to track all code changes via jira.
My point was, in this case, comment in the original jira is sufficient for any
errata.txt updates related to it. Opening a new jira to just update it seems
unnecessary overhead.
So errata.txt change be committed with a comment like "Update errata.txt for
HIVE-16743".
Yes, updating document errata.txt process after discussion in a JIRA sounds
like a good idea. (Yes, I don't think we need to have a DISCUSSION/VOTE thread
for this one)
> Update errata.txt for HIVE-16743
> --------------------------------
>
> Key: HIVE-16760
> URL: https://issues.apache.org/jira/browse/HIVE-16760
> Project: Hive
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Wei Zheng
> Assignee: Wei Zheng
> Attachments: HIVE-16760.patch
>
>
> Refer to:
> https://issues.apache.org/jira/browse/HIVE-16743?focusedCommentId=16024139&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16024139
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
