| 16 Nov 2025 |
 dotlambda | I think this is more confusing than helpful and in the future, staging-next-26.05 should only be created after the last merge of staging next into master before branch-off | 15:10:00 |
 leona | We currently auto merge
master -> staging-next -> staging
master -> staging-next-25.11 -> staging-25.11
| 15:10:13 |
| leona | You don’t want staging-25.11 to exist in this stage too? This was an explicit wish by multiple contributors because previously they forgot to backport PRs from staging that didn’t reach the release | 15:11:27 |
| leona | I mean yes, we could of course create staging-next-25.11 only at the time of branch off | 15:12:26 |
| dotlambda | The latter of those automatic merges will have to be changed anyway (from master to release-25.11) so until that time why not directly merge master into staging-25.11? | 15:13:27 |
| dotlambda | In reply to @leona:leona.is
You don’t want staging-25.11 to exist in this stage too? This was an explicit wish by multiple contributors because previously they forgot to backport PRs from staging that didn’t reach the release It certainly should. I only talking about -next | 15:13:58 |
| dotlambda | * It certainly should. I'm only talking about -next | 15:15:03 |
