[
https://issues.apache.org/jira/browse/HBASE-25515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell updated HBASE-25515:
----------------------------------------
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. (was: 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. Perhaps something can be created that takes the union of git branch
listing and reporter.a.o release version history. )
> At a glance git branch release history tool
> -------------------------------------------
>
> Key: HBASE-25515
> URL: https://issues.apache.org/jira/browse/HBASE-25515
> Project: HBase
> Issue Type: Task
> Reporter: Andrew Kyle Purtell
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
