| 10 Oct 2024 |
 Tristan Ross | I don't really understand what happened since I was just waking up lol | 01:51:54 |
 SigmaSquadron | In reply to @hexa:lossy.network
the person on the off-topic room? yeah there was also another one in the dev room a while back; don't remember the nick | 01:57:30 |
 hexa | comes with the job ig | 02:06:39 |
| Tristan Ross | Wait, you're getting paid? (/s) | 02:07:43 |
| hexa | roughly the same amount as emily | 02:08:05 |
| hexa | you're not doing release-management for free, are you? | 02:08:30 |
| Tristan Ross | I am doing it for free. | 02:08:42 |
| hexa | huh 😄 | 02:08:54 |
|  NixOS Moderation Botchanged room power levels. | 02:11:45 |
| Tristan Ross |
NixOS Moderation Bot changed the power level of Tristan Ross from Default to Moderator.
Huh?
| 02:14:16 |
| hexa | 🪄 | 02:14:28 |
| hexa | have we spent any thought on the redis situation? | 13:25:18 |
| Tristan Ross | In reply to @hexa:lossy.network
have we spent any thought on the redis situation? I might need a reminder on what the situation even is | 15:28:28 |
 emily | are the freeze dates the first day at which breaking changes are disallowed or the last day that they are allowed? and what timezone do we use? | 16:01:53 |
| emily | i.e. do breaking changes to release critical packages need merging today on the 10th or can they be merged tomorrow on the 11th too? | 16:02:09 |
 leona | In reply to @rosscomputerguy:matrix.org
I might need a reminder on what the situation even is They also changed their license to SSPL: https://redis.io/blog/redis-adopts-dual-source-available-licensing/ | 16:03:33 |
| Tristan Ross | In reply to @emilazy:matrix.org
are the freeze dates the first day at which breaking changes are disallowed or the last day that they are allowed? and what timezone do we use? There's specific dates of when the freeze is done in the schedule | 16:03:46 |
| emily | I know | 16:03:53 |
| emily | they don't answer my question which is about whether the interval is open or closed | 16:04:04 |
| Tristan Ross |
Nov 8th: Unrestrict all breaking changes; new changes will not be present in master before branch-off
| 16:04:11 |
| emily | I'm confused. I'm talking about the October 11 deadline | 16:04:22 |
| Tristan Ross | I would say that as soon as Oct 11th hits, no breaking changes. | 16:04:54 |
| emily | ok | 16:05:06 |
| emily | in which timezone? | 16:05:10 |
| emily | (no breaking changes to release-critical packages, right? the schedule implies that every other package can be broken until the 25th) | 16:05:37 |
| Tristan Ross | AoE | 16:05:42 |
| Tristan Ross | In reply to @emilazy:matrix.org
(no breaking changes to release-critical packages, right? the schedule implies that every other package can be broken until the 25th) Yeah, only critical packages like GCC, LLVM, etc just cannot be broken. | 16:06:17 |
| Tristan Ross | https://nixos.github.io/release-wiki/Release-Critical-Packages.html | 16:06:46 |
| Tristan Ross |
The implications of RFC 0085 are that these packages can not have breaking changes applied to them for six weeks leading up to a release date.
| 16:07:03 |
| emily | mhm | 16:08:54 |
