24 Sep 2024 |
hexa | or else we're running into a support cycle issue | 21:42:49 |
Tristan Ross | In reply to @hexa:lossy.network Tristan Ross: please make sure, that 24.11 get's released with go 1.23 as the default Alright | 21:43:36 |
Tristan Ross | I'll take a look at what I can tonight, if there's a relevant PR then please ping me in it. | 21:44:12 |
hexa | no, there isn't | 21:46:02 |
hexa | but go is always critically lagging behind, because it needs a treewide change with a potential for updating the vendor hashes | 21:46:23 |
Tristan Ross | In reply to @hexa:lossy.network but go is always critically lagging behind, because it needs a treewide change with a potential for updating the vendor hashes Oh, well we can look into it and make sure it happens. We have some time before breaking changes are restricted. | 21:59:11 |
25 Sep 2024 |
Tristan Ross | hexa: https://github.com/NixOS/nixpkgs/pull/342429 I think you might've missed this lol | 01:49:43 |
Fabián Heredia | Currently on staging-next :3
https://github.com/NixOS/nixpkgs/commit/350a819a36b585257d7ed19f07ab6169e4a0cd35 | 02:06:25 |
Tristan Ross | Yep | 02:17:02 |
hexa | OK! | 08:13:52 |
26 Sep 2024 |
| Fabián Heredia set a profile picture. | 01:15:56 |
27 Sep 2024 |
Tristan Ross | Is there a script to generate the release blockers / feature freeze issue for pinging the right ecosystems and packages? | 16:43:02 |
Tristan Ross | Oh, there is | 16:43:39 |
Lily Foster | In reply to @rosscomputerguy:matrix.org Is there a script to generate the release blockers / feature freeze issue for pinging the right ecosystems and packages? i mean it's in wiki | 16:43:41 |
Lily Foster | https://nixos.github.io/release-wiki/Feature-Freeze-Announcement.html | 16:43:47 |
Tristan Ross | In reply to @lily:lily.flowers i mean it's in wiki Yeah, I just didn't notice it until now | 16:43:53 |
Tristan Ross | Also, that page is out of date lol | 16:44:27 |
Tristan Ross | It should say it's under the scripts subdir but it doesn't | 16:44:38 |
Tristan Ross | Since we've never had a lix team before, which category should I place them under on the feature freeze announcement? I have 3 ideas: Languages ecosystem, Programs, or Core. | 17:01:55 |
Tristan Ross | https://github.com/NixOS/nixpkgs/issues/344920 | 17:16:12 |
1 Oct 2024 |
| hardfloppy joined the room. | 16:48:54 |
| -_o joined the room. | 21:00:20 |
4 Oct 2024 |
| @ajcxz0:matrix.org left the room. | 01:00:46 |
5 Oct 2024 |
| jeroen joined the room. | 13:59:30 |
7 Oct 2024 |
Randy Eckenrode | The Darwin rework stuff is targeting the next staging-next cycle. If the cycle starts late, how does that interact with the freeze? | 04:30:33 |
| emily joined the room. | 04:33:52 |
| Austin Horstman joined the room. | 04:46:19 |
| aviallon ⚡️ joined the room. | 10:34:15 |
| aviallon ⚡️ | 10:34:19 |
Tristan Ross | In reply to @reckenrode:matrix.org The Darwin rework stuff is targeting the next staging-next cycle. If the cycle starts late, how does that interact with the freeze? For one, the PR should be merged before the 11th. On the 30th, we have a staging-next -> master merge. | 15:47:59 |