| 13 May 2025 |
|  Honnip joined the room. | 06:30:11 |
 Alyssa Ross | Would be nice if we could have a staging-25.05 branch already, or at least a label, so we don't have to keep track of which PRs need backporting out of band until branch-off. | 13:53:48 |
 emily | yeah I think we discussed last release that we should probably branch staging off before master | 13:54:13 |
| emily | or just do the whole branch-off at the same moment staging opens up for breaking changes | 13:54:27 |
 leona | I will now just create it. I didn't find it in the last release discussion and nobody mentioned it (before Grimmauld (any/all) a few days ago | 13:56:00 |
 vcunat | From the current staging-next, I assume. | 13:56:47 |
| emily | IIRC I don't think it's part of the standard procedures to do it at this point. (it would just be an improvement on the standard procedures) | 13:58:43 |
| Alyssa Ross | A 25.11 release notes document would also be nice so we could start collecting descriptions of breaking changes on staging. | 15:00:25 |
| emily | I personally think it would be nice if there was never a point where we can't land breaking changes somewhere (but I guess the idea of having a freeze prior to branch-off is to focus efforts on ZHF?) | 15:05:14 |
| emily | i.e. we would just branch off everything at the exact point of the freeze | 15:05:32 |
 Fernando Rodrigues | I would also really like that. | 15:05:48 |
| Alyssa Ross | that would make sense | 15:05:50 |
