Osquery uses basic SQL commands to leverage a relational data-model to describe a device.

osquery

We can discuss whether to call 5.10.1 stable, or how to approach this in office hours, or here, I guess

This might be a dumb question, but if there's a known stability issue in 5.10.1 and 5.10.2 includes a patch that addresses the stability issue, why would we not mark 5.10.2 as stable?

That’s kinda my view — I’m biased towards 5.10.2

The counter argument would be that it’s an acceptable instability and we want stable faster.

But I don’t think that’s super compelling

On the other thread I suggested to not release 5.10.1 as-is (originally I was suggesting the revert of that feature).
As for making stable faster, the ES FIM fix is the only relevant change from 5.10.1, it's localized and the change minimal, so it doesn't seem necessary to me to wait more due to it.

I think accepting other unknown issues from localized stuff is ok, otherwise we would never release. I would only block/add time if the fix/change is on core functionality which affects everyone.

So in short, I would "drop" 5.10.1 and make 5.10.2 the candidate release, and mark it as stable, maybe tomorrow after office hours if everyone agrees?