If you plan on voting YES on the new committeeMinSize proposal, you're better off waiting until the resolution of the Increase Tx and Block Mem Units proposal has concluded. Why?
1) If it passes, the committeeMinSize proposal becomes null and void anyway.
2) If it does not pass, then the committeeMinSize proposal remains in play.
What?
A parameter update proposal must reference the last enacted parameter update action when it is submitted. If two live actions of the same type point to the same previous update, only one can pass. As soon as one does, the new "last enacted parameter change" changes, meaning the other proposal now has an incorrect previous GA reference.
What was the last parameter update you ask?
"Plutus V3 Cost Model" in Nov 2024 (b2a591ac219ce6dcca5847e0248015209c7cb0436aa6bd6863d0c1f152a60bc5#0)
Could this have been avoided?
Yes. If the existing parameter GA was expected to pass then you can have two live parameter changes by pre-emptively referencing the live action GA. This approach was first witnessed on SanchoNet, and then on mainnet during the two update CC GAs recently.
Should you vote now or later? I guess it depends on how much you value your time.
I have plenty of other views on this whole scenario but those will be going into my rationale eventually.