Release Management | 316 Members | |
| 25.05 "Warbler" | https://nixos.github.io/release-wiki/Home.html | 84 Servers |
| Sender | Message | Time |
|---|---|---|
| 9 Oct 2025 | ||
| That wouldn't ease the amount of work for contributors which was my primary concern. | 16:28:15 | |
| * That wouldn't ease the amount of work for contributors, which was my primary concern. | 16:28:30 | |
| Fixes will typically be easy per package, and eligible for backporting, of course. | 16:29:41 | |
In reply to @vcunat:matrix.org My concern is more with the stability of the 25.11 release. Backporting is also more work so I would say it would have been ok | 16:29:41 | |
| Making such a major change just before release is bound to make stuff break in untested ways | 16:30:26 | |
| Still, we have like 6 weeks until branch-off, you know, so I'd hope it will be OK by then 😉 | 16:30:27 | |
In reply to @vcunat:matrix.orgLet's hope | 16:30:44 | |
| Active contributors very often follow master or unstable. | 16:31:23 | |
| * Active contributors very often follow master or unstable, I believe. | 16:31:51 | |
| https://github.com/NixOS/nixpkgs/issues/445447 | 16:32:28 | |
In reply to @vcunat:matrix.org I honestly can not do that. The last time I did that, something significant broke and I didn't really have time to fix stuff on such short notice due to Uni work. I also couldn't downgrade easily due to version incompatibilities. That's why I like keeping my prod and personal machines on stable. Though I still prefer unstable for sw development and test VMs | 16:35:41 | |
| Sure, I meant it as an argument why commonly used stuff should get fixed before the branch-off. | 16:36:41 | |
| Though yeah, by glancing at that issue, lots of work that doesn't seem worth the benefits 😢 | 16:38:30 | |
| hehe there's 19 more I went to mention on the ticket 👻 surely | 16:40:57 | |
| * hehe there's 19 more I went to mention on the ticket 👻 surely this can be detected | 16:41:12 | |
| I think some was hacking a script to get all log files and grep them. | 16:41:44 | |
| (specifically mentioned around that cmake 4 upgrade) | 16:42:10 | |
| aha | 16:42:15 | |
given that you can even do nix log -f. attribute... | 16:43:01 | |
| 10 Oct 2025 | ||
| hi, with previous releases the release artworks got asked for and committed to https://github.com/NixOS/nixos-artwork/ that repo got replaced with https://github.com/NixOS/branding and a blank wiki page https://wiki.nixos.org/wiki/Artwork the branding repo has no mention of the previous release artworks https://github.com/search?q=repo%3ANixOS%2Fbranding%20%22Warbler%22&type=code djacu – who did this change – is not in this channel and I do not want to have contact with them. I justed wanted to let you know, that this will be come a problem if we want to continue having release artworks. I did three artworks, for 23.11, 24.05, 24.11. (to be honest, this nonsense changes and blind activism primarily by such "branding" efforts is driving me further away from the community. this is not a front against you all in this channel, it's just … stupid actions by some (who are not in this channel I guess.) | 07:13:24 | |
| please do correct me if I misunderstood something, I hope so I did | 07:16:07 | |
| I already asked djacu about how release images work with the new branding repo. The only real change is that we would like to have some sort of vector image. How exactly we integrate it there, I don’t know yet, will see on that. But jopejoe1 and I will open a “search for release logo” post on discourse soon :) | 07:17:49 | |
| OK, could you link me that convo, if it is public? | 07:19:14 | |
| The real work is getting the art. Moving to another place should be easy whenever. | 07:19:29 | |
| I agree vcunat, as I previously did that work. unfortunately a living Xantusia is outside of my reach to snap a picture. I'd recommend on not violating copyright laws, as was done previously most time. | 07:21:47 | |
| I am not looking for trouble, and see all the work that is put into the release. I do feel a shift and grift to the community with such changes that should be discussed elsewhere I guess. | 07:22:44 | |
| Branding looks very much in scope of the marketing team, in my eyes. | 07:23:20 | |
| It’s currently not, unfortunately. There is not much more then a few other guideline suggestions (no AI, release under open license, adhere to branding guide) and for it to be a discourse thread instead of issue + PRs | 07:23:25 | |
| * | 07:24:02 | |
| thats how it's evolving in the last ~12 months yea, by such changes pushed by some. | 07:24:05 | |