hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stack <st...@duboce.net>
Subject Re: [DISCUSS] 2.1.1 Release Plans?
Date Mon, 08 Oct 2018 23:34:23 GMT
On Mon, Oct 8, 2018 at 4:01 PM Josh Elser <elserj@apache.org> wrote:

> Best place to find hbck2 issue needing review is off of HBASE-19121 or
> somewhere else?
>
>
For 2.1.1 issues, see the 2.1.1 release listing:
https://issues.apache.org/jira/projects/HBASE/versions/12343470 Half these
items are items turned up testing branch-2.1 and trying to use hbck2. Will
link a few others.


> All: please feel free to ping directly if you want/need reviews.
>
> Will do.

Thanks,
S



> On 10/5/18 7:41 PM, 张铎(Duo Zhang) wrote:
> > Stack has a plan on the 2.1.1 release where we want to finish the first
> > version on hbck2. In the real deploy we have met a stuck cluster several
> > times, and lots of users have asked that why hbck can not work any
> more...
> >
> > So the current opening issue is not important, please help reviewing the
> > patches for hbck2 to speed up the release...
> >
> > Thanks for bringing this up
> >
> > Mike Drob <mdrob@apache.org>于2018年10月5日 周五23:53写道:
> >
> >> Devs,
> >>
> >> It's been almost 3 months since 2.1.0 was released (Jul 19) and we have
> 150
> >> commits on branch-2.1 in that time. What do folks think of getting a
> >> release going? I know that there's been some discussion around the HBCK2
> >> stuff landing, but I feel like the conversation has gotten a bit lost
> >> without an actual release to relate to.
> >>
> >> Duo, as the 2.1.0 release manager, are you interested in maintaining the
> >> 2.1 branch release cadence? If you've gotten busy, then let's find
> another
> >> volunteer.
> >>
> >> There are 18 issues open or in progress currently. Only one is labelled
> >> blocker, and five more are critical -- let's evaluate these and the
> rest to
> >> figure out what we need for a release to happen. I went ahead and
> created a
> >> 2.1.2 version in Jira so that we have somewhere to move issues that
> aren't
> >> getting done soon.
> >>
> >> Meanwhile, I think we also need to look at test stabilization --
> there's 15
> >> tests on the dashboard that might need attention.
> >>
> >> Mike
> >>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message