Release Management | 341 Members | |
| 25.11 "Xantusia" | https://nixos.github.io/release-wiki/Home.html | 91 Servers |
| Sender | Message | Time |
|---|---|---|
| 18 Apr 2024 | ||
| AoE? | 12:01:32 | |
| Anywhere on Earth | 12:01:57 | |
| The update should be non-breaking (which I thought the deadline for breaking changes outside of a few core packages was May 1). | 12:02:19 | |
| * The libiconv update should be non-breaking (which I thought the deadline for breaking changes outside of a few core packages was May 1). | 12:02:26 | |
| The LTO stuff would have to be a release team call. I’ve been assuming not making it. Just wanted to expand on the clang change. It mostly does nothing right now, but it’s required for LTO once ld64 is updated. | 12:03:40 | |
| I can cherry-pick the fixes to my libiconv and get that PR back into ready for review. They mostly concern being ready to build/link with the updated ld64. I had a race condition in one of my meson.build files that the ld64 update exposed. | 12:05:59 | |
| * I can cherry-pick the fixes to my libiconv and get that PR back into ready for review. They mostly concern being ready to build/link with the updated ld64. I had a race condition in one of my meson.build files that the ld64 update exposed. (Edit: and an incompatibility in Kyua) | 12:10:31 | |
| 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 | |
| * 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 | |
| * 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 | |
| * 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 | |
| Uh wow, I didn't know that meson.build hyperlink "works" 😲 | 12:14:00 | |
| * Uh wow, I didn't know that meson.build hyperlink "works" 😲 (off topic, really) | 12:15:16 | |
| 14:54:55 | ||
| 19 Apr 2024 | ||
| 14:05:10 | ||
| 21 Apr 2024 | ||
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 | |
In reply to @arianvp:matrix.orghttps://nixos.github.io/release-wiki/Branch-Off.html | 13:23:41 | |
| thanks! | 13:25:38 | |
| I guess I'll ahve to update that document regarding the AWS AMIs | 13:25:47 | |
| 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 | |
| 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 | |
| I understand, thanks | 13:51:01 | |
| For the upcoming meeting for RMs and REs, the main points of the meeting I would like to address:
| 17:15:25 | |
| Link to the meeting: https://jitsi.lassul.us/nixos-2405 | 17:57:33 | |
| 18:35:10 | |
| Things I would like to see in the release notes:
| 18:42:07 | |
| Any guidelines on how granular we want the commits and PRs to be? | 21:37:24 | |
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 | |
* 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 | |
* 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 | |