Software development takes time and has many unanticipated challenges that makes time estimation difficult. When developers do provide estimates users, managers etc then get stroppy when they slip by.
Therefore the best strategy is just to ignore requests for time schedules because it’s a no win situation.
I think you might be confusing estimates and fixed-cadence releases. It’s really simple to provide a promise of fixed-cadence releases - just take whatever changes are merged (if any) and release them on the cadence.
Promising to release a specific feature within a specified timeframe is a different beast entirely.
Nothing about OP’s question indicated they were interested to know if there was a regular release schedule. Specifically they asked for the next release, therefore I tried to explain why there may not be a simple answer to their question.
I think you might be confusing estimates and fixed-cadence releases. It’s really simple to provide a promise of fixed-cadence releases - just take whatever changes are merged (if any) and release them on the cadence.
Promising to release a specific feature within a specified timeframe is a different beast entirely.
Nothing about OP’s question indicated they were interested to know if there was a regular release schedule. Specifically they asked for the next release, therefore I tried to explain why there may not be a simple answer to their question.