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

osquery

Q: how often will osquery create a new release? either major/minor version

We're currently aiming for approximately every 2 months. It's not very formal

can we aim for faster release for minor version?
actually because my company would like to use the feature from `a851d85`
<https://github.com/osquery/osquery/compare/4.3.0...master>

current 4.3.0 release is on Apr 14th, not sure whether Apr 30th is possible for 4.3.1 (half month)?

Unless there’s a critical bug. probably not. Curring releases is still fairly labor intensive. So ~2 months is mostly a balance between releasing often, and not burning out. We’re trying to get it more automated though

I kind of had that question on official vs "dirty" binaries. "4.2.0-30-g09c52468-dirty" -- anyone can just compile a dirty and use vs the fully stable tested release or is there other downsides?

It’s an open source piece of software, you can do whatever you want with it. :slightly_smiling_face:
Maintaining a local fork, either for one release of forever, isn’t inherently wrong

The version comes from git, “dirty” indicates you have uncommited changes. The `-30` indicates it’s 30 commits past the tag. And the sha is the git sha. Mostly that’s there to help in tracking down what build someone is running.

If you ask for help about some kind of crash, and it’s specific to a custom build, there’s not much folks can help with.

But broadly speaking, I’d expect master to be shipable, and there’s not a very rigorous process for testing before a release

Oh no it was just a pulled and compiled as you said - just debating on if i want to over write the my compiled with the official 4.3.0 - I mainly did the compiled for creating a MSI at the time

“no”? I can tell you the version is basically tyhe output of `git describe --tags --always`

No, as in not asking for help - just a general question ; )

I understand what you mean and appreciated the response

Several sites maintain local builds. It’s not wrong. It’s just more work

&gt; Unless there’s a critical bug. probably not. Curring releases is still fairly labor intensive. So ~2 months is mostly a balance between releasing often, and not burning out. We’re trying to get it more automated though
understand, I can create custom build based on commit first