 | Release Management | 344 Members |
| 25.11 "Xantusia" | https://nixos.github.io/release-wiki/Home.html | 94 Servers |
| Release Management | 344 Members |
| 25.11 "Xantusia" | https://nixos.github.io/release-wiki/Home.html | 94 Servers |
| Sender | Message | Time |
|---|---|---|
| 18 Apr 2024 | ||
 Randy Eckenrode | That incompatibility is a reason to target post-24.05 IMO. Apple changed the linker in Xcode 14 to disallow nested static archives. The ecosystem should have adjusted by now, but there may be packages that haven’t yet. (Kyua had not.) | 12:11:38 |
| Randy Eckenrode | * That incompatibility is a reason to target post-24.05 IMO. Apple changed ld64 in Xcode 14 to disallow nested static archives. The ecosystem should have adjusted by now, but there may be packages that haven’t yet. (Kyua had not.) | 12:11:47 |
| Randy Eckenrode | * That incompatibility is a reason to target post-24.05 IMO. Apple changed ld64 in Xcode 14 to disallow nested static archives. The ecosystem should have adjusted by now, but there may be packages that haven’t yet (like Kyua). | 12:12:00 |
| Randy Eckenrode | * That incompatibility is a reason to target post-24.05 IMO. Apple changed ld64 in Xcode 14 to disallow nested static archives. The ecosystem should have adjusted by now, but there may be packages that haven’t yet (like Kyua). I tested with ld-prime, and it has the same behavior. It must have been an accident it worked before. | 12:12:18 |
 Vladimír Čunát | Uh wow, I didn't know that meson.build hyperlink "works" 😲 | 12:14:00 |
| Vladimír Čunát | * Uh wow, I didn't know that meson.build hyperlink "works" 😲 (off topic, really) | 12:15:16 |
 @ajaxbits:matrix.org left the room. | 14:54:55 | |
| 19 Apr 2024 | ||
 @mathieu:kainnef.com joined the room. | 14:05:10 | |
| 21 Apr 2024 | ||
 Arian | Question. Why did we reset the revCount in 23.11 ? https://github.com/NixOS/nixpkgs/commit/dc7b3febf8d862328d8704de5c8437d2df442c76Where does the magic number 551362 come from? | 13:08:33 |
 raitobezarius | In reply to @arianvp:matrix.orghttps://nixos.github.io/release-wiki/Branch-Off.html | 13:23:41 |
| Arian | thanks! | 13:25:38 |
| Arian | I guess I'll ahve to update that document regarding the AWS AMIs | 13:25:47 |
 @stablejoy:matrix.org | Im reading the release wiki and following here. What can a beginner do to help? Its exciting but not sure how could I help | 13:44:37 |
| raitobezarius | There's two tasks a beginner can do: (a) You can look at pick up the garbage: https://github.com/NixOS/nixpkgs/projects/18?query=is%3Aopen+sort%3Aupdated-desc -- only if you have expertise with the aforementioned software, otherwise you may just create needless noise for people (b) Wait for the Zero Hydra Failure process where the goal is to minimize all the failures | 13:49:54 |
| @stablejoy:matrix.org | I understand, thanks | 13:51:01 |
 jonringer | For the upcoming meeting for RMs and REs, the main points of the meeting I would like to address:
| 17:15:25 |
 Weijia | Link to the meeting: https://jitsi.lassul.us/nixos-2405 | 17:57:33 |
| jonringer |
| 18:35:10 |
| jonringer | Things I would like to see in the release notes:
| 18:42:07 |
 @jacg:matrix.org | Any guidelines on how granular we want the commits and PRs to be? | 21:37:24 |
| @jacg:matrix.org | Should we change package names to inline code blocks (backticks) and match the package's pkgs attribute name? For example, should things like 'YouTrack is bumped to 2023.3. become 'youtrack is bumped to 2023.3.' ? | 21:42:08 |
| @jacg:matrix.org | * Should we change package names to inline code blocks (backticks) and match the package's pkgs attribute name? For example, should things like 'YouTrack is bumped to 2023.3.' become youtrack is bumped to 2023.3.' ? | 21:42:29 |
| @jacg:matrix.org | * Should we change package names to inline code blocks (backticks) and match the package's pkgs attribute name? For example, should things like "YouTrack is bumped to 2023.3." become "youtrack is bumped to 2023.3." ? | 21:42:54 |
| @jacg:matrix.org | Concerning 'Ensure that the affected programs/services appear at the beginning of the release note" are we happy with "The mpich package expression now requires ..." or should this become something like "mpich: the package expression now requires ..." ? | 21:46:26 |
| @jacg:matrix.org | * Concerning "Ensure that the affected programs/services appear at the beginning of the release note" are we happy with "The mpich package expression now requires ..." or should this become something like "mpich: the package expression now requires ..." ? | 21:50:11 |
 teto | jonringer: might I enquire why the quote of my pending PR description ? Is the descriptio not good enough :'( ? | 22:27:40 |
| 22 Apr 2024 | ||
| @jacg:matrix.org | teto: In yesterday's meeting the release editors were asked to ensure that the name of the affected package or service appear at the beginning of each note, for easy visual parsing/filtering of items. Yours was simply given as an example of a note where the package name first appears further in the text of the note. | 07:02:39 |
| jonringer | Yea, that was all | 14:39:27 |
| jonringer | You PR was just the first PR with the Appreciate what you do for lua and vim :) | 17:30:54 |
| jonringer | When referencing packages in release notes, example: https://github.com/NixOS/nixpkgs/pull/305965/files#r1575114124. I feel like we should:
Not sure how people feel about my suggestion here. This fixates more on the nixos option rather than project itself. | 17:37:52 |