| 30 Sep 2022 |
| Jitsi widget removed by  Janne Heß | 15:48:19 |
| 3 Oct 2022 |
 Winter (she/her) | hexa: are you going off an unpublished list for the feature freeze? i ask since at least one team that's in the list and has the feature freeze flag set wasn't pinged (it's the "blockchains" team, since apparently we have that) | 11:35:58 |
| Winter (she/her) | i know you said you cut it down or something | 11:36:08 |
 hexa | there is an open PR, that shows the relevant changes I made; the blockchains team doesn't maintain … anything as far as I can tell fwiw | 11:37:00 |
| hexa | https://github.com/NixOS/nixpkgs/pull/194151 | 11:37:19 |
| Winter (she/her) | In reply to @hexa:lossy.network
there is an open PR, that shows the relevant changes I made; the blockchains team doesn't maintain … anything as far as I can tell fwiw i couldn't find that pr after searching for "maintainers", thanks github | 11:37:54 |
| Winter (she/her) | thanks! | 11:37:57 |
| hexa | https://github.com/NixOS/nixpkgs/issues/194208 | 11:40:21 |
| hexa changed the room topic to "Release schedule: https://github.com/NixOS/nixpkgs/issues/193585 | Feature Freeze: https://github.com/NixOS/nixpkgs/issues/194208 | Blockers: https://github.com/orgs/NixOS/projects/13" from "Release schedule: https://github.com/NixOS/nixpkgs/issues/193585". | 11:40:53 |
| 11 Oct 2022 |
| Winter (she/her) | @hexa and I started working on some more "full-featured" release notes, starting with libxcrypt stuff: https://md.darmstadt.ccc.de/q3fYCibVSu6dpmt3D9ptTg?both cc @Mic92 @Janne Heß | 02:50:42 |
| hexa | editing requires an account, but registration using an email address is possible | 03:24:48 |
 Mic92 | In reply to @winterqt:nixos.dev
@hexa and I started working on some more "full-featured" release notes, starting with libxcrypt stuff: https://md.darmstadt.ccc.de/q3fYCibVSu6dpmt3D9ptTg?both cc @Mic92 @Janne Heß Thx. I will have a look a it latest during the nixos meetup this thursday. | 14:15:53 |
|  raphi joined the room. | 20:33:17 |
| raphi | question: feature freeze is at 2022-10-31
the github issue (https://github.com/NixOS/nixpkgs/issues/193585) says that the affected branches are staging and staging-next, this would imply that breaking changes to master are allowed, which seems weird to me. i'd expect breaking changes are also prohibited in master. is my understanding correct, or are breaking changes still allowed in master after that date? | 20:37:42 |
| Janne Heß | In reply to @raphi:tapesoftware.net
question: feature freeze is at 2022-10-31
the github issue (https://github.com/NixOS/nixpkgs/issues/193585) says that the affected branches are staging and staging-next, this would imply that breaking changes to master are allowed, which seems weird to me. i'd expect breaking changes are also prohibited in master. is my understanding correct, or are breaking changes still allowed in master after that date? I think the middle section of this comment sums it up: https://github.com/NixOS/rfcs/pull/85#issuecomment-812288951 | 20:40:14 |
| Janne Heß |
For clarification, this has no implication on master. The changes to master should be able to be captured for each PR, and we can effectively move "green to green". These restrictions are more in regard to staging, where most PRs we may verify by building just a downstream package and/or run a test or two to verify it's not "absolutely broken"; but these often cause other packages to break.
| 20:40:19 |
| 14 Oct 2022 |
| Mic92 | Winter (she/her): I had a look yesterday at the release notes. I think from all package upgrade a summarized changelog based on the nix changelogs posted in discourse would read the most interesting. | 07:53:13 |
| Winter (she/her) | In reply to @joerg:thalheim.io
Winter (she/her): I had a look yesterday at the release notes. I think from all package upgrade a summarized changelog based on the nix changelogs posted in discourse would read the most interesting. "from all package upgrade"? | 11:38:30 |
| Mic92 | * Winter (she/her): I had a look yesterday at the release notes. I think the most interesting package in the all package upgrades section is a summarized nix package manager changelog based on the changelogs posted on discourse. | 11:42:03 |
| Mic92 | In reply to @winterqt:nixos.dev
"from all package upgrade"? Sorry, this was not clear at all. I edited my previous response. I was already doing something else while writing this. | 11:42:34 |
| Mic92 | Are you on NixCon by chance? | 11:43:11 |
| Winter (she/her) | In reply to @joerg:thalheim.io
Are you on NixCon by chance? Assuming you're asking about attending in-person. no. | 11:45:12 |
| Winter (she/her) | In reply to @joerg:thalheim.io
Sorry, this was not clear at all. I edited my previous response. I was already doing something else while writing this. Makes sense now, and agreed -- I'm just mainly concerned about some wording. But we can figure that out later. | 11:45:41 |
| Mic92 | Get the words out and than I make a read through. I also have some software for improving writeups that works great. | 11:46:15 |
| Winter (she/her) | Oh? What is it, if I may ask? | 11:47:15 |
| Mic92 | Winter (she/her): https://instatext.io/ | 11:49:51 |
| 15 Oct 2022 |
|  underpantsgnome! changed their display name from underpantsgnome to underpantsgnome!. | 00:30:48 |
| 22 Oct 2022 |
 sterni | Why is there no 22.11-pre tag yet? are they only created at branch off? Seems a bit annoying that git describe and nixos-version give different results for the same commit | 19:43:19 |
| sterni | i.e. 22.11pre415026.598f83ebeb2 vs 22.05-pre-81519-g598f83ebeb2 | 19:43:45 |
| hexa | master is tagged with 22.11-pre after the 22.05 branch-off | 19:45:32 |
