OpenTracing -> OpenTelemetry :) For me, I think the OpenTelemetry part is a blocker, we must finish it before cutting an RC since the current implementation is already landed on branch-2.5 and it breaks some Otel best practises, so we should not release it out.
Now it is only Nick doing the work and Tak Lon Wu and I reviewing the PRs. And I also joined the CNCF slack channel and saw Nick is working hard in communication with the Otel community on how to better implement tracing in HBase, for example, how to trace big scans. I would encourage more people in our community to involve so we can make progress faster. Thanks. Sean Busbey <bus...@apache.org> 于2021年12月9日周四 10:02写道： > If we don't want to wait for HBASE-26543 (fix arg parsing for shell) > then we should revert HBASE-24772 from branch-2.5 prior to an RC. > > > On Wed, Dec 8, 2021 at 7:34 PM Andrew Purtell <apurt...@apache.org> wrote: > > > > As your branch-2.5 RM I am assembling a list of work items that should be > > completed before a 2.5.0RC0 candidate is submitted for the PMC's > > consideration. > > > > I have so far: > > > > - OpenTracing span naming convention and coverage improvements. > > > > - Shell exit code fixes/improvements. > > > > - The "encryption improvements umbrella". Arguable, but let's include it > > for now. Can all be resolved as Later if need be. > > > > Let's discuss what else, if anything, should be on this list, or if one > or > > more of the above items does not constitute a release blocker. I consider > > incomplete work-in-progress a blocker. Obviously all of the work in > > progress should land before release. For WIP, let's also agree on a > > definition of done. > > > > -- > > Best regards, > > Andrew > > > > Words like orphans lost among the crosstalk, meaning torn from truth's > > decrepit hands > > - A23, Crosstalk >
