| 5 Dec 2025 |
leona | and also it would need much more hydra capacity and also maintainer capacity to make staging cycles much less breaking | 10:46:04 |
leona | also somehow find out how to not break users use cases too mcuh | 10:46:22 |
leona | * also somehow find out how to not break users use cases too much | 10:46:23 |
vcunat | Well, some people pay for 10+ years of stable support in some distros... | 10:47:54 |
vcunat | Breaking changes are unavoidable and some people don't want to deal with them continuously. I can understand that. | 10:49:38 |
emily | for many things having a defined process of adding a new version, ensuring everyone migrates to it, and then dropping the old one would be the same total work on Hydra but without breaking systems.
OTOH it's churn in terms of packaging/codebase and it fundamentally relies on expecting maintainers to be responsive
| 10:49:39 |
emily | I don't think doing more jobsets would be that bad though, as long as the results can actually be triaged to maintainers. because after all we would be saving all the builds we spend on stable releases anyway | 10:50:29 |
emily | but it all comes down to having responsive maintainers and the tooling to triage things to them IMO, otherwise we can't avoid breaking things for half a year and then scrambling for ZHF regardless 😅 | 10:51:48 |
vcunat | There are intentional incompatibilities, too. You have to do those at some points. (That's what I meant by "unavoidable".) | 10:53:19 |
emily | right, hence ^. OTOH I do think that with better tooling we could achieve "6 months of deprecation before it breaks" for more things. | 11:03:55 |
emily | (so you could still just let warnings pile up and solve them every n months, to some extent) | 11:04:13 |
emily | question is how much work it'd be compared to maintaining a stable branch - and how many tooling improvements we'd need | 11:04:37 |
emily | I hate dealing with compat and multiple versions, but if it was sufficiently streamlined and we had processes that reliably cleaned those up over time, it might be nicer than dealing with branches. | 11:05:39 |
emily | (and even "safe" backports on stable branches do break people's deployments, sometimes) | 11:06:30 |
lennart | (gonna catchup on backlog soonish :} ) | 11:11:27 |
lennart | ok caught up: could anyone reading this who has an opinion, please reply if a
👍️ if they think, I should follow through with a discourse post, to open up this discussion
👎️ if they think, the status quo is OK and works as intended
thanks! | 12:50:56 |
lennart | * ok caught up: could anyone reading this who has an opinion, please react if a
👍️ if they think, I should follow through with a discourse post, to open up this discussion
👎️ if they think, the status quo is OK and works as intended
thanks! | 12:51:03 |
lennart | * ok caught up: could anyone reading this who has an opinion, please react if a
👍️ if they think, I should follow through with a discourse post, to open up this discussion
👎️ if they think, the status quo is OK and works as intended (no post)
thanks! | 12:51:17 |
lennart | I really am undecided and don't have enough insight into this topic | 12:51:50 |
lennart | * ok caught up: could anyone reading this who has an opinion, please react if a
👍️ if they think, I should follow through with a discourse post, to open up this discussion
👎️ if they think, no further post is needed
thanks! | 12:53:39 |
| 7 Dec 2025 |
| Robert Evans joined the room. | 18:46:47 |
| Robert Evans set a profile picture. | 19:02:49 |
| 8 Dec 2025 |
raboof | I see there's no staging-next-25.11 - does that just mean the current staging-25.11 will become staging-next-25.11? when? is there anything in particular I can do to help that along? :) | 15:53:22 |
vcunat | We have that branch in progress now:
https://github.com/NixOS/nixpkgs/pull/468267 | 15:56:12 |
vcunat | The general workflow is described at
https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#staging | 15:57:02 |
vcunat | (hopefully well enough - or we should fix it there) | 15:57:18 |
raboof | huh must've missed a 'fetch' | 15:59:10 |
| 9 Dec 2025 |
| mate joined the room. | 12:35:36 |
| adamcstephens changed their profile picture. | 17:25:20 |
| adamcstephens changed their profile picture. | 17:48:39 |