[
https://issues.apache.org/jira/browse/HBASE-28844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883649#comment-17883649
]
Duo Zhang commented on HBASE-28844:
-----------------------------------
OK, there is a problem that, we cut branch-2 and after some time we released
2.0.0, so there are some issues have two commits in the git repo, one for the
master branch and one for branch-2. So if we check the commits to branch-3
after cutting branch-2, we will also get these commits but they do not have fix
versions 3.0.0-* on jira, as they have fix version 2.0.0.
So we need to filter out these issues...
> Align the fixed issues in git and jira
> --------------------------------------
>
> Key: HBASE-28844
> URL: https://issues.apache.org/jira/browse/HBASE-28844
> Project: HBase
> Issue Type: Sub-task
> Components: community
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Attachments: CHANGELOG.3.0.0-alpha-1.md, CHANGELOG.3.0.0-alpha-2.md,
> CHANGELOG.3.0.0-alpha-3.md, CHANGELOG.3.0.0-alpha-4.md,
> CHANGELOG.3.0.0-beta-1.md, CHANGELOG.3.0.0-beta-2.md, in_git_3.0.0.txt
>
>
> The API cleanup is almost done, so we are entering the last steps for
> releasing the final 3.0.0.
> We should try our best to align the fixed issues in git and jira, especially
> for a major release.
> It will be a huge project, so file a jira issue to track this work.
> Plan to do this in the next few weeks, waiting for my 192GB machine to ready
> so I can start to run ITBLL and upgrading tests locally(Actually I've already
> bought everything for the machine but it failed to boot with 192G DDR5 RAM so
> I sent the motherboard back...)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
