Ok, updated https://github.com/facebook/osquery/issues/2819 with my quick set of notes, I will wait until tomorrow to cut a release either way. I made a tracker for the next-next (2.3.0): https://github.com/facebook/osquery/milestone/32 and will use that to prioritize issues for the that release, which I will aim to complete by next Thursday. We may be able to get #2819 hammered out and into 2.2.0, but for the mean time I will add it to 2.3.0. Always eager for feedback on how to manage releases, the best we have is creating a milestone 😕 No one seems to manage release blocking features other than "please can I get this in" and Github doesn't make this easy-- so we hammer onward-- the best we can.