Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
We do not have a single source of truth as to what are active branches and what was the most recent release by version number made from each branch. If we had such a resource, then committers could refer to it whenever merging PRs or cherry picking commits backward. When merging a PR into a branch or committing a cherry pick it is important that the committer, at that time, go to JIRA and update fix versions on the corresponding issue, so that at the next release the change will be correctly included in the change log. Perhaps something can be created that takes the union of git branch listing and reporter.a.o release version history.
Attachments
Issue Links
- is related to
-
HBASE-22853 Git/Jira Release Audit Tool
- Resolved