On 2025-02-07 18:00:35 +0100 (+0100), René Ribaud wrote:
[...]
> 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.

These are all great suggestions! I applaud your desire to dig into
options for improving the contributor experience, and also suggest
you consider getting involved in the ongoing Bridging the Gap
effort. See this earlier thread for links to resources and ideas for
where we could use some additional help moving things forward:

https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/GTPTFUPXXBDMWNQZGZDLM2IIX4FSTT5Y/

--
Jeremy Stanley