Block the release #4455
Description
The next automatic release is coming up on Saturday, and it stresses me out; I feel we have a few questions to answer first before we simply ship what's on master right now. Here's an incomplete list:
- We need a decision on Better support for shell aliases #4385. I asked a few stakeholders about this here and here, but didn't get much feedback.
- We made a change to the
wcommand (commit without hooks), which seems to be controversial. The discussion there stalled, so I'm unsure if we need to change something about it before we ship it. - I have quite a large number of PRs open right now, and I'd like some clarity which of these should be included in the next release.
- I feel that "focus the main view" and the cherry-pick/revert series are both too big; they both make fundamental changes and have a pretty high risk of introducing regressions, so it's probably best to merge them only after the release, to give us some time to test them on master and work out the kinks.
- I'm unsure about "move commits to new branch"; it's a nice improvement that I have been using a few times myself now, it's good to have; but maybe it needs more testing too
- Most of the other ones are nice QoL improvements that would be a shame not to include; but none of them is important enough to be marked as blocks-release individually