Repository navigation
Preferred workflow for remaining bug fixes #6207
Replies: 3 comments
|
@NathanFreeman @matyhtf Hi guys. I just noticed 6.3.0 RC1 has been tagged. There are still a lot of unresolved bugs in master, some of which may have security implications. I've got PRs open for all of them. Will these all be addressed before 6.3.0 is released? |
|
Thank you for continuing to submit these fixes. At present, we are not in a hurry to merge these PRs. All related PRs need to be carefully reviewed, including code correctness, compatibility, security impact, and regression risk. |
|
@NathanFreeman Understood. Thanks for the clarification, and thanks to you and @matyhtf for reviewing and merging so many of my PRs already. I’ve now rebased all the remaining PRs onto their current target branches. I’d appreciate it if you could work through them when you have a chance, as keeping them all updated takes considerable ongoing work. |
Uh oh!
There was an error while loading. Please reload this page.
Hi @matyhtf,
I’d appreciate your guidance on handling the remaining Swoole fixes I’ve identified.
I have roughly 30 verified bugs left, in addition to the PRs already open. I’ve kept fixes in small, isolated PRs because that was requested and makes each change easier to review. However, continuing at the current pace may create a large review queue for you and a lot of ongoing rebasing work for me.
Would you prefer that I:
I want to keep the review workload manageable and avoid unnecessary work for everyone. Thanks.
All reactions