[
https://issues.apache.org/jira/browse/PHOENIX-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated PHOENIX-6314:
----------------------------------
Affects Version/s: 5.0.0
4.15.0
> Utility to identify git commit / Jira fixVersion discrepancies for RC
> preparation
> ---------------------------------------------------------------------------------
>
> Key: PHOENIX-6314
> URL: https://issues.apache.org/jira/browse/PHOENIX-6314
> Project: Phoenix
> Issue Type: Task
> Affects Versions: 5.0.0, 4.15.0
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Fix For: 5.1.0, 4.16.0
>
>
> As part of RC preparation, we need to identify all git commits that landed
> on release branch, however their corresponding Jira is either not resolved
> yet or does not contain expected fixVersions. Only when we have git commits
> and corresponding Jiras with expected fixVersion resolved, we get all such
> Jiras included in auto-generated CHANGES.md as per Yetus changelog generator.
> Proposal of this Jira is to provide such script that can be useful for all
> upcoming RC preparations and list down all Jiras where we need manual
> intervention. This utility script should use Jira API to retrieve individual
> fields and use git log to loop through commit history.
> The script should identify these issues:
> # commit is reverted as per commit message
> # commit does not contain Jira number format PHOENIX-XXXX in message
> # Jira does not have expected fixVersion
> # Jira has expected fixVersion, but it is not yet resolved
> It can take inputs as:
> # First commit hash to start excluding commits from history
> # Fix Version
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
