So, @clong, we haven't pushed to apt/yum yet because there might be an issue with 3.3.0 that we're currently tracking down. We've been seeing issues with registering our extension in production, and turns out this was the reason we haven't completed our rollout, and I tagged 3.3.0 as stable without realizing that 😞 My bad. So, we're trying to sort out what the issue is and get some assurances on what's up before we complete the release 😕 I'm happy to update release notes, and the binaries are available on the site, however we're holding off on updating something that folks auto update from until we know whats up