chore: Review older open pull requests for 3.3. inclusion

[terriko]

I'm just opening an issue so this will show up in the 3.3 release milestone and I won't forget to do it.

We've got a number of pull requests that have been languishing for a while for various reasons (often due to my availability, but some actually don't work or are causing test fails). As part of preparing for the 3.3. release this fall (currently targeting late September 2023) I need to go through these and see what state those are in and figure out which ones should go into the release, which ones should be closed, and which ones can be left open but won't be part of 3.3.

If anyone wants to help: I would be very happy if anyone else has time to do code review on these and help either make them ready to merge or let me know if you think they're not viable. Comment in individual PRs or here to get my attention!

[rudrakshkarpe]

Hey @terriko! I'd like to help with the 3.3 release. While I'm not sure if I can review PRs as a contributor, I'm willing to assist in any way I can. Let me know how I can contribute to making this release a success! 🚀

[terriko]

@rudrakshkarpe If you've got some time, I'm pretty sure #2892 just needs a test fix before it can be merged. If you can pull that branch and figure out exactly what we need to fix, that could be super helpful!

If you've never grabbed someone else's branch before, there's instructions in github's web interface but it's basically:

git checkout -b Rexbeast2-issue_2821 main
git pull git@github.com:Rexbeast2/cve-bin-tool.git issue_2821

You won't be able to push to the original branch, but you can modify your copy and push it to your own fork to share and then I could merge your working one (github should take care of credit appropriately so it'll show as being worked on by multiple people).

[rudrakshkarpe]

@rudrakshkarpe If you've got some time, I'm pretty sure #2892 just needs a test fix before it can be merged. If you can pull that branch and figure out exactly what we need to fix, that could be super helpful!

If you've never grabbed someone else's branch before, there's instructions in github's web interface but it's basically:

git checkout -b Rexbeast2-issue_2821 main
git pull git@github.com:Rexbeast2/cve-bin-tool.git issue_2821

You won't be able to push to the original branch, but you can modify your copy and push it to your own fork to share and then I could merge your working one (github should take care of credit appropriately so it'll show as being worked on by multiple people).

Ohh! That's pretty interesting. I'll look into it asap!

[terriko]

I think I'm at the point where I pushed what I had time to push and I should close this. But anyone is always welcome to poke old pull requests if they want!