Channels
doorman
infrastructure
random
zercurity
community-feeds
fleet-dev
code-review
queryhub
apple-silicon
carving
tls
fim
goquery
zentral
aws
querycon
golang
zeek
file-carving
fuzzing
auditing-warroom
linen-dev
fleetosquery
plugins
jobs
arm-architecture
darkbytes
process-auditing
uptycs
android_tests
selfgroup
vendor-feeds
fleet
eclecticiq-polylogyx-extension
ebpf
website
core
general
macos
kolide
osctrl
extensions
foundation
sql
officehours
linux
windows
Title
a
Alejandro
12/28/2020, 3:43 PMOut of curiosity, is there any documentation on how the versioning works on osquery? Trying to understand the reasoning of going on a new minor version vs going a patch version? And what we should expect in terms of backwards compatibility or changes in tables etc?. Thanks
t
theopolis
12/28/2020, 3:54 PMUnsure if versioning is written down in an easily discoverable place (vs. bi-weekly office hours notes). Minor versions are released ideally at bi-monthly cadence, they represent a milestone we identify and work towards, tracked on GitHub as an issue milestone. Patch releases are reserved for when we need to fix an unforeseen bug as part of a minor release. Revision releases are reserved for build-time changes.
Major releases are where we stack on several compatibility changes.
Ideally everything is backwards compatible except for major releases, and if that’s not the case then the release notes on GitHub will call out the change.
a
Alejandro
12/28/2020, 5:53 PMBrilliant, thanks Ted for the detailed info that clarifies a lot