<@U6EFFT5FG> merged the BPF changes in, and that w...
# core
s
@alessandrogario merged the BPF changes in, and that was a thing we wanted to try to get out. How’s m1 support? Should I cut 5.1 today, or do folks want to wait? (@Mike Myers)
❤️ 1
a
Thanks for merging it! We are in the process of removing some of the additional messages we left in each commit (due to the squashes)
I would say in a day or two we can mark it as ready for review
Once that is merged, we are going to focus again on the codesigning workflow
s
Er, mike merged it. I thought you did. Either way, it’s merged.
😄 1
So, do you you want a 5.1 release, or do you want to wait?
a
I think we could make a 5.1 release and include additional crash fixes (if any)
then maybe proceed with a test release for M1?
s
If you’re planning on getting people to test head, we can just wait and see if we need to merge anytthing else before cutting 5.1
a
and use that to double check that you and @zwass can verify it contains everything it needs to be correctly supported
s
Just about my EoD. So I’m not going to pick this up. But I think we can cut a 5.1 whenever.
a
I'll leave the HEAD running on a couple of our systems, then we can talk about 5.1 tomorrow when you have time!
s
y’all automated it enough, it’s easy 🙂
m
thanks for being ready to move on the 5.1 release! I think it'll mostly be the BPF fix. The M1 changes may be ready to review but that alone will take a bit I expect
a
I'll spend some time today and tomorrow to do some additional testing, and I'd like to maybe make one of the limits configurable with a command line flag
then we can talk about 5.1 monday?
👍 1
s
Okay! My time next week is going to be really scarce (Child has the week off from school) but we should be able to cut a release Mon or Tues
ty 1