@reubenv I see you are starting to do the release and are triaging tickets, thanks!
I just made a change on this ticket, though, and moved it back to the 2.23.0 release:
It was in “post commit code-review” state and had already been committed, so I just closed the ticket and changed the fix version back to 2.23.0.
This is the basic process I use when using a release… I’d look at all the open tickets in the 2.23.0, but if they are still open it doesn’t necessarily mean they aren’t in the release… many just have never been fully closed. I review each ticket and look at the commit history for the module and decide whether it needs to be changed to 2.24.0 or just closed as fixed. If there are any questions regarding it, I’ll ask the committer on the ticket. Let me know if that makes sense!
I think most of the other tickets you changed are in the same state (Code Review Post Commit) and can just be closed and moved back to 2.23.0. (Generally if I enter a bug and then fix it myself, I don’t close it, I leave it in Code Review Post-Commit in case anyone wants to weigh in after the fact, as a second pair of eyes is always good, but if they haven’t by the time the release happens I just close it myself)