| 31 Mar 2025 |
 emily | even 2.24 took a couple tries to stick | 21:15:30 |
| emily | and I advocated for that bump | 21:15:37 |
| emily | because I don't think the drift is good for the projects | 21:15:49 |
| emily | but the only way to solve the root cause is proactive communication and prioritization of Nixpkgs' needs and concerns for a critical component | 21:16:19 |
 John Ericson | Ultimately I will prioritize a good healthy working relationship over not delaying the split package 6 months more | 21:17:05 |
| John Ericson | but please ask yourself | 21:17:08 |
| John Ericson | the list of things above | 21:17:12 |
| John Ericson | it looks entirely like static known issues to me | 21:17:23 |
| John Ericson | I am a bit scared for 2.28 right now, yes, because that is where unknown-unknowns come from | 21:17:39 |
| John Ericson | but you already proposed we do just that (and monopackage) | 21:17:53 |
| emily | nothing blocks shipping a patching mechanism that works with both packagings in 25.06 and backporting to 24.11, right? | 21:18:00 |
| John Ericson | the marginial cost of the split package feels very low to me | 21:18:09 |
