What's everyone's feeling on setting a date for <h...
# core
m
What's everyone's feeling on setting a date for https://github.com/osquery/osquery/milestone/49 ?
Because we have a CVE, I think there's good reason to make movement on the release. Let me know if Stefano's time is needed, I can try to bring him back for that
1
I know everyone is busy right now, but can we set a goal date for the release process? Whose time is needed?
s
I can help with the process this Friday, starting from writing the changelog and prepare some test builds. What do you all think? Would be cool to have https://github.com/osquery/osquery/pull/6414 and https://github.com/osquery/osquery/pull/6413 in that, so I'll address the review there first, then I can start on the release process.
💯 1
s
TBH I think this is mostly waiting on #6413 and #6414, which are both approved and in Stefano’s court to merge. I think the other two things things aren’t going to happen fast enough
s
@seph If by "not going to happen fast enough", you mean the release process, Friday, I agree, but the question was more "is everyone ok if we start to prepare it?". We have to start somewhere 😄
s
Er, I mean https://github.com/osquery/osquery/pull/5901 and https://github.com/osquery/osquery/issues/6411 are probably not going to merge fast enough to be part of 4.4.0 and should be pushed to the next release
s
aaah sorry milestone!
s
I’ve moved those to 4.5.0 for clarity. I’m good with us cutting pre-release builds as soon as your container PRs merge
🎉 2
t
I have a doc fix I can PR tonight
👍 1
s
Whatever is merged, is awesome 🙂 Stick it in the milestone if you want to make sure we hold for it
👍 1
m
We have @Stefano Bonicatti available today to help with the milestone, but one thing that came up is that we really want Alessandro's Windows event publisher PR merged so I added it to the milestone, and we think that's not going to delay (already reviewed, just needs some nitpick fixes to get approval)
s
I’m 👍 waiting if you want to get #6280 in. And, TBH anything else you have that’s basically ready to go.
s
To add to that, I'm not going to tag today, but I will start the process, at least writing the changelog and preparing clean VMs to do builds, which takes a while. But ideally Monday or Tuesday would be nice to have the tag, changelog and packages ready 🙂
🙏 1
s
I can probably help with changelogs as well
s
ok, I'm going to merge the two PRs now since they will effectively have the same change to be done, so I'll just open it on a new PR. As for the changelog, do you want to split it in half? (As in half the merged PRS)
And each work on one? @seph?
s
Not sure? It doesn’t feel like it splits easily One of us should take a pass. Want me to start?
s
If you want, definitely 😄 I can prepare my VMs then
s
I’ll try to start. sure.
t
Ok I will try to sneak in a PR or two tonight then. I promise small fixes :)
😄 1
I just reviewed the Windows Event publisher PR. I requested some changes and I am available most of the weekend to iterate.
I submitted all the PRs I had planned. If you folks are around this weekend TTYL
m
@Stefano Bonicatti @alessandrogario is it possible to get this PR feedback addressed in time for 4.4.0?