!aGqRytqbCECitOFhbt:nixos.org

Release Management

339 Members
25.11 "Xantusia" | https://nixos.github.io/release-wiki/Home.html93 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
7 Apr 2025
@scrumplex:duckhub.ioScrumplexYear of the Matrix platform!16:51:12
@leona:leona.isleona lennart: https://github.com/NixOS/nixos-artwork/issues/146 16:55:16
9 Apr 2025
@me:linj.techlinj leona: Tristan Ross Maybe release managers need to know this (libgccgit?) issue. 10:07:51
@me:linj.techlinj * leona: Tristan Ross Maybe release managers need to know this (libgccgit?) issue. 10:08:08
@leona:leona.isleonagood to know, i know some people are working on 15.4 issues in staging currently. but will still keep an eye on that10:09:55
@me:linj.techlinj * leona: Tristan Ross Maybe release managers need to know this (libgccjit?) issue. 11:02:55
@reckenrode:matrix.orgRandy EckenrodeIf we need to switch to the system libc++, it would be a technically breaking change. I believe other options are being explored first for 25.05.16:55:06
@leona:leona.isleonaif it's necessary it's okay, you all do a good job :)19:19:56
10 Apr 2025
@reckenrode:matrix.orgRandy Eckenrode We’re still figuring it out. That’s an option. Switching the ABI namespace is an option. Using emily’s SDK fixup is an option. 12:11:30
13 Apr 2025
@reckenrode:matrix.orgRandy EckenrodeI’ll be opening the PR later today once a regression test finishes building. It changes the ABI namespace while using the system libc++abi. It’s technically breaking but in practice should have minimal impact.17:11:11
@reckenrode:matrix.orgRandy EckenrodeIt’s going to be tomorrow. Breaking libtorch-bin is too breaking. I’m testing using the system libc++ (while keeping those changes, which are good for compatibility when you need LLVM’s libc++).20:57:28
16 Apr 2025
@terrorjack:matrix.orgterrorjack joined the room.20:22:30
17 Apr 2025
@reckenrode:matrix.orgRandy Eckenrode Using the system libc++ worked. It took a bit longer due to wanting to make sure things built, but https://github.com/NixOS/nixpkgs/pull/398727 to ready last night. I think emily is going to review it in the next few days. I know there was a tentative approval, but I wanted to post it here for consideration and feedback. If this is too much too quickly, I can revert the system libc++ changes in the PR, so they can be unreverted after branch. 12:04:28
18 Apr 2025
@tgerbet:matrix.orgtgerbetAs a pre notification I'm likely to request an exception to BC change restriction for nginx next week. NixOS and nginx release are aligned in May and they plan to start their new cycles next week https://mailman.nginx.org/pipermail/nginx/2025-April/F4F33YXMJPZMQ4VKG3WJPNGSIEFFBMKX.html Not bumping means we will have to maintain EOL nginx versions which is not great.18:30:48
@leona:leona.isleonaack, ok!18:31:31
19 Apr 2025
@jopejoe1:matrix.orgjopejoe1 (4094@39c3) changed their display name from jopejoe1 to jopejoe1 (4094@eh22).13:01:20
21 Apr 2025
@gerryd:matrix.orggerryd joined the room.15:24:59
22 Apr 2025
@emilazy:matrix.orgemily leona: requesting potential freeze exemption for https://github.com/NixOS/nixpkgs/pull/400646 (and its dependency https://github.com/NixOS/nixpkgs/pull/400427), and https://github.com/NixOS/nixpkgs/pull/397398. (because my test build of the latter is running into some unrelated-looking diffutils build issue and I don't know that I'll have the time to investigate tonight, and I'd like to understand https://github.com/NixOS/nixpkgs/pull/400739 a little better before hitting the button on the libGL one). I project minimal impact since these are mostly just deprecations and fixes that could technically break someone doing something incredibly bizarre. 22:01:48
@emilazy:matrix.orgemily(actually, I'm not sure if we're already meant to be in the freeze, because it's already the 23rd in anywhere-on-Earth time, but I've been interpreting the intent as "once it is no longer the 22nd anywhere on Earth")22:03:36
@emilazy:matrix.orgemily * ( actually, I'm not sure if we're already meant to be in the freeze, because it's already the 23rd in anywhere-on-Earth time, but I've been interpreting the intent as "once it is no longer the 22nd anywhere on Earth" never mind, inverted the sign in my head 🫠) 22:04:30
@leona:leona.isleonaFor this time I intend it to be 23rd AoE end of day, i.e. in about 36 hours I think22:05:46
@leona:leona.isleonaIf it’s still a problem then, I can have a more in depth look, but it seems okay for me22:06:43
@emilazy:matrix.orgemilyaha, okay. I'd expect "2025-04-24 – Restrict all breaking changes" for that (rather than -23), but that's the release wiki's fault 😅22:07:09
@emilazy:matrix.orgemilyhopefully will be able to sort it out in the next 36 hours, yes.22:07:18
@leona:leona.isleonaTime zones are super confusing and I don’t want to make anyone angry about 24 hours so that’s why I decided to it this way. I will think about better wording, also for the release wiki22:08:34
@leona:leona.isleonaFor most of the days it’s pretty irrelevant anyways, just for the freezes22:09:11
@emilazy:matrix.orgemilyyes, for sure, timezones are a mess22:11:52
@emilazy:matrix.orgemily "something is okay if it's the last day it's meant to be allowed anywhere on the planet" is a sensible general principle, I think. the problem is that if something becomes allowed on a certain date, then "anywhere on Earth" is no longer one timezone but two, since you want the earliest possible date for that :) 22:12:52

Show newer messages


Back to Room ListRoom Version: 6