I'm scheduled to remove 2.0 related materials tomorrow, so I'd really like us to avoid restarting that clock.
As far as known issues, just make sure the affected version(s) include 2.0.6 and call it a day. On Thu, Sep 19, 2019 at 11:04 AM Stack <[email protected]> wrote: > > First, good find Guanghao. Thanks for the fix. > > I can roll RCs for branch-2 (Would be good to do it after > hbase-operator-tools goes out because then these new releases become > candidates for the stable pointer). > > On branch-2.0, given its EOM, I could add a 'KNOWN_ISSUES.md' file to > http://apache.mirrors.lucidnetworks.net/hbase/2.1.6/ and list this issue in > it. Then update the note in the download page to point at new known issues > doc? (Suggestions appreciated). > > S > > > > On Wed, Sep 18, 2019 at 5:55 PM Guanghao Zhang <[email protected]> wrote: > > > Only 2.2.1, 2.1.6 and 2.0.6 are effected. Earlier releases are fine. Please > > avoid downloading these releases. If you already running these versions in > > your cluster, please use splitormerge_switch to disable region merge > > now. See HBASE-23044 for more details. > > > > Need to rolling new release for branch-2.1 and branch-2.2 line. Ping @stack > > for branch-2.0, do we need a more release 2.0.7? > > > > Thanks > > Guanghao Zhang > >
