You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2024/09/24 06:18:00 UTC
[jira] [Comment Edited] (HBASE-28844) Align the fixed issues in git and jira
[ https://issues.apache.org/jira/browse/HBASE-28844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883657#comment-17883657 ]
Duo Zhang edited comment on HBASE-28844 at 9/24/24 6:17 AM:
------------------------------------------------------------
These issues are in branch-2.0 before releasing 2.0.0 but not in branch-3. Let me check these issues first.
{noformat}
HBASE-12350 Backport
HBASE-17553 Make a 2.0.0 Release
HBASE-18187 Release hbase-2.0.0-alpha-1
HBASE-18190 Set version
HBASE-18282 Forward port in HBASE-20054
HBASE-18431 Addressing compatibility issue between 1.x and 2.x, not needed in 3.x
HBASE-18514 Backport
HBASE-18594 Release hbase-2.0.0-alpha2
HBASE-18595 Set version
HBASE-18615 Test failure on branch-2
HBASE-18653 2.x only change
HBASE-18817 2.x only change
HBASE-18819 Set version
HBASE-18828 Generate CHANGES.txt for 2.x
HBASE-18833 Backport personality script from master to all other branches
HBASE-18933 Set version
HBASE-18945 Typo in commit message(HBSE-18945), there is an addendum in branch-2 but not in master so we get this on branch-2
HBASE-19197 Move version on branch-2 from 2.0.0-alpha4 to 2.0.0-beta-1.SNAPSHOT
HBASE-19315 Set version
HBASE-19407 2.x only change
HBASE-19648 Set version
HBASE-19670 2.x only change
HBASE-19716 Fix test on branch-2
HBASE-19860 2.x only Jenkins file change for debugging
HBASE-19888 Set version
HBASE-20113 Set version
HBASE-20142 Copy doc from master to branch-2
HBASE-20233 Missed in master
HBASE-20246 2.0 only change
HBASE-20247 Set version
HBASE-20415 2.0 only change
HBASE-20462 Put up 2.0.0RC1
HBASE-204642.0 only change
{noformat}
was (Author: apache9):
These issues are in branch-2.0 before releasing 2.0.0 but not in branch-3. Let me check these issues first.
{noformat}
HBASE-12350
HBASE-17553
HBASE-18187
HBASE-18190
HBASE-18282
HBASE-18431
HBASE-18514
HBASE-18594
HBASE-18595
HBASE-18615
HBASE-18653
HBASE-18817
HBASE-18819
HBASE-18828
HBASE-18833
HBASE-18933
HBASE-18945
HBASE-19197
HBASE-19315
HBASE-19407
HBASE-19648
HBASE-19670
HBASE-19716
HBASE-19860
HBASE-19888
HBASE-20113
HBASE-20142
HBASE-20233
HBASE-20246
HBASE-20247
HBASE-20415
HBASE-20462
HBASE-20464
{noformat}
> 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_2.0.0.txt, 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)