Kicking this thread
The first 2.0.6 release candidate has been posted. I tested starting
branch-2.2 over the tip of branch-2.0 and seemed to work fine on my little
setup (data formats are not incompatible at least). I did not run the
rolling upgrade recipe [1].
Will post an ANNOUNCE that
Thank you for prioritizing the upgrade experience for the cautious
upgrader!
On Wed, Apr 24, 2019 at 6:38 AM 张铎(Duo Zhang) wrote:
> I think we'd better make a 2.0.6 release after 2.2.0 it out, and make sure
> that it is fine to upgrade to 2.2.0 from 2.0.6, and then EOL the 2.0.x
> release line.
Is it not possible to go from 2.0.5 to 2.2.0? We have to do the 2.0.6? (I'm
game. Just wondering if we have to).
Thanks,
S
On Wed, Apr 24, 2019 at 6:38 AM 张铎(Duo Zhang) wrote:
> I think we'd better make a 2.0.6 release after 2.2.0 it out, and make sure
> that it is fine to upgrade to 2.2.0 from
Okay, so a 2.0.6 some time after 2.2.0 comes out, then a month later EOL?
Do we have a volunteer to RM a 2.0.6? Stack I think you're still listed as RM
for 2.0, you up for it?
On 2019/04/24 13:37:58, 张铎(Duo Zhang) wrote:
> I think we'd better make a 2.0.6 release after 2.2.0 it out, and make
I'v checked the issues in version 2.0.6 [1], seems no critial issues, so
for me +1.
1.
https://issues.apache.org/jira/issues/?jql=project%20%3D%20HBASE%20AND%20fixVersion%20%3D%202.0.6
On Wed, Apr 24, 2019 at 8:37 PM Sean Busbey wrote:
> Hi folks!
>
> Tomorrow will be a month since the 2.0.5
Hi folks!
Tomorrow will be a month since the 2.0.5 release, which was noted:
> NOTICE: We plan on this being the last release on branch-2.0 (unless
critical issues found).
Any objections to me doing the cleanup + announcement for formally
shutting down the release line?
