On Mon, Oct 8, 2018 at 8:19 AM Mike Drob <md...@apache.org> wrote: > Thanks for pointing me to that discussion, Duo. I've updated HBASE-19121 to > have fix version 2.1.1 and 2.0.3 so that it is easier (at least for me) to > find via Jira. > > I was thinking HBASE-19121 more an umbrella to hang hbck2 stuff off. Would suggest we unschedule 2.1.1/2.0.3 as target.
> I'll start looking at the hbck2 patches and will leave comments there. > > There are a lot of subtasks against that issue, it is unclear to me which > ones are critical and which ones are not for a release. > > They usually have a target fix but let me give them another pass. Not all have to land in 2.1.1/2.0.3. Since hbck2 tool is in a different repo, have we thought about what the > release actions would look like? Do we need to have two votes going at the > same time? Can we release core repo with an hbck service in master, but > release the hbck tool sometime later? This first release is going to be > more complex I think; would be good if somebody can figure that out in > parallel so we're not blocked on it later. > > Yeah, the point of hbck2 being a separate repo was so they could have different release cadences. It would be good if the first hbck2 release happened around 2.1.1 release time. I can work on this part. S > Mike > > On Fri, Oct 5, 2018 at 6:41 PM 张铎(Duo Zhang) <palomino...@gmail.com> > 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 <md...@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 > > > > > >
