| 18 Apr 2025 |
 emily | (but also just that the freeze schedule is designed around the normal procedures where everything is being batched together) | 16:36:10 |
| emily | anyway, freeze exceptions are not uncommon so it shouldn't be a big issue, but it's not sounding to me like there are remaining issues of the kind that would prevent a merge into staging | 16:36:53 |
 maralorn | Anyway the way I read the release schedule it says "2025-05-08 unrestrict all breaking changes on staging" for me the natural conclusion is: Everything that hits staging before -05-08 will reach the release. | 16:41:08 |
| maralorn | You are. And you are free to fix or maintain any package you want. However your vibes are not actionable for anyone else and if you insist on that mode you are the only one who can approve a merge. So I will do you the favor of ignoring that. Feel free to announce any package you want to have working before the merge at any time though. | 16:45:20 |
| emily | right but we do ideally try to have a cycle without breaking changes | 16:50:19 |
| emily | since even fixes/minor bumps can cause enough headaches | 16:50:33 |
| emily | though of course that can happen after branch-off, but we don't always get as many -next cycles as we'd like | 16:50:53 |
| emily | sometimes all the last-minute breaking changes pile into one cycle and then we need another one to clean up remaining carnage :P | 16:51:14 |
| emily | anyway, since the Haskell stuff has received so much testing I don't anticipate great issues. (but AIUI the cases where Haskell stuff interacts with the rest of the system don't get as much testing, so I do think landing soon would be good) | 16:51:49 |
| emily | (like, maybe a major ShellCheck or Pandoc bump might break stuff. I don't know if those are in the pipeline, just an example of a fire we might have to put out during a -next cycle) | 16:52:15 |
|  petrockette changed their profile picture. | 17:38:09 |
| 19 Apr 2025 |
 sterni | maralorn: looks like HLS/hlint are the last big things from the report. Musl/Static stuff can be ignored and needs to be reevaluated in staging(-next). thielema package failures look weird, maybe worth a bug report upstream. large-records is not fixable for the moment. | 09:57:18 |
