What else can I do to help drive this? I'm using this filter to look at pending issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D% 20HTRACE%20AND%20%22Target%20Version%2Fs%22%20%3D%204.2%20AN D%20status%20!%3D%20resolved%20ORDER%20BY%20priority%20ASC I have a patch up for HTRACE-346, and think that everything else could feasibly be pushed to the next version. Mike <https://issues.apache.org/jira/browse/HTRACE-381> On Fri, Aug 26, 2016 at 1:54 PM, Colin McCabe <[email protected]> wrote: > On Fri, Aug 26, 2016, at 07:06, Mike Drob wrote: > > HTrace devs, > > > > It's been a while since our last update, and it looks like there are > > several good fixes slated for the 4.2 version. What do you all think > > about > > releasing soon? > > +1. > > > > > There's a few issues that I think are close to wrapping up, or could be > > included soon, but I didn't see any blockers in JIRA. The only question > > in > > my mind is how close we are on HTRACE-376 > > <https://issues.apache.org/jira/browse/HTRACE-376>. > > I think it's ready to submit. It makes HTrace more generally useful, > extending it to use-cases where you need finer granularlity than > milliseconds-- and it does it in a fully backwards-compatible way. The > 4.2 release probably would go more smoothly if we bumped HTRACE-376 to > 4.3, though. > > cheers, > Colin > > > > > Meanwhile, can somebody create a 4.3 version in JIRA so that incomplete > > issues have a place to go? > > > > Thanks, > > Mike >
