As written that we're voting on, we'd merge the feature to trunk whenever it's ready (shared definition of "ready" TBD) and the next alpha will have that new feature available. Or, if it's right at the end of the cycle, that new feature would first show up in a release in -beta1.
When you say "how we manage the case", can you elaborate on what the challenges or tension is that you're thinking of? I feel like there's something you're seeing as a challenge that I'm missing and want to make sure we don't miss it. On Wed, Nov 19, 2025, at 1:53 PM, Dmitry Konstantinov wrote: > I am trying to understand how we manage the case when a feature is ready to > merge into trunk but we have a set of alpha versions released..
