Hi Jay,

Unfortunately, there is no magic here.
Extending the review bandwidth doesn’t seem possible at the moment.

However, I see something we should focus on:
If a feature misses the release freeze, it still has a "fresh" review. To avoid losing context and focus, we should aim to keep the momentum and try to prioritize it so that it gets merged as early as possible in the next cycle.

We should also try to review well ahead of the release freeze to prevent last-minute changes that might cause a feature to slip again.

The key is to minimize feature rollovers from cycle to cycle as much as possible, as it can be really demotivating and lead to a loss of self-confidence. At least, that’s how it felt for me.

Of course, I understand that there are plenty of valid reasons why this happens, and unfortunately, it will happen again.