27 Sep 2024 |
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 |
Randy Eckenrode | I’m hoping it’s merged well before the 11th. | 15:49:05 |
emily | if the staging-next cycle starts after the 11th, does it really matter when the PR is merged? | 15:49:05 |
emily | (I don't know how likely that is though) | 15:49:11 |
emily | there's already breaking changes in the next staging and the cycle will happen when it happens anyway | 15:49:23 |
Randy Eckenrode | The issue is this cycle is taking a bit longer and cause the next one go later. | 15:49:31 |
vcunat | There's a period when no breaking changes are allowed. | 15:49:35 |
emily | I assumed the cutoff was more about not piling more breaking changes into the next cycle | 15:49:36 |
vcunat | * There's a period when no breaking changes are allowed to be merged. | 15:49:44 |
emily | (but I assume the schedule did not anticipate the weird timing of this current cycle) | 15:50:03 |
Randy Eckenrode | In reply to @vcunat:matrix.org There's a period when no breaking changes are allowed to be merged. I’m trying to get ahead of that, but the targeted cycle that wasn’t past the freeze may go late. | 15:50:24 |
Randy Eckenrode | Does that mean merged into staging or staging-next into master? That’s my point of confusion. | 15:50:57 |
emily | (surely "On the 30th, we have a staging-next -> master merge." is just projected, anyway? you can't say for certain when a staging cycle will be ready to merge into master ) | 15:51:47 |