[
https://issues.apache.org/jira/browse/PHOENIX-6316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266141#comment-17266141
]
ASF GitHub Bot commented on PHOENIX-6316:
-----------------------------------------
stoty closed pull request #1091:
URL: https://github.com/apache/phoenix/pull/1091
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> git_jira_fix_version_check.py should identify fixed Jira without any commit
> ---------------------------------------------------------------------------
>
> Key: PHOENIX-6316
> URL: https://issues.apache.org/jira/browse/PHOENIX-6316
> Project: Phoenix
> Issue Type: Task
> Affects Versions: 5.0.0
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Fix For: 5.1.0
>
>
> Now that we have script git_jira_fix_version_check to identify all commits
> that have no corresponding Jira with expected fixVersion available, we should
> also let it figure out the diff the other way around i.e identify all Jiras
> that are marked resolved with given fixVersion but have no commit present
> with Jira number included.
> RC preparation also needs to find this diff because we don't want to provide
> extra Jira in CHANGELOG without any corresponding commits present on git
> (unless it is svn checkin and fixVersion is relevant).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
