| 17 Mar 2022 |
 hexa | Regular reminder that we need a release blockers project for 22.05, please! | 21:58:45 |
| hexa | and while we're at it, one for 22.11 would be nice as well | 21:58:58 |
| hexa | some things can be put on a schedule early | 21:59:06 |
| hexa | apparently projects aren't privilege gated on the org (any more?) | 23:04:23 |
 Janne Heß | created both | 23:05:36 |
| Janne Heß | 22.05 - https://github.com/orgs/NixOS/projects/12
22.11 - https://github.com/orgs/NixOS/projects/13 | 23:06:10 |
|  ghishadow joined the room. | 23:08:05 |
| 18 Mar 2022 |
 Vladimír Čunát | And the "blocker" label is also for similar purpose? | 05:43:49 |
|  malo joined the room. | 21:04:20 |
| malo | hexa suggested that I post here letting folks now about, https://malob.github.io/nix-review-tools-reports/, in case it might be of use during the ZHF push. | 21:19:26 |
 tomberek | malob: that is excellent, thank you | 21:19:54 |
| malo changed their display name from malob to malo. | 21:28:24 |
| 19 Mar 2022 |
| Janne Heß | Does anyone know the purpose of the 22.05 milestone? It seems kind of redundant to the org-wide project to me. Or is there something nice about it I haven't noticed yet? | 23:32:11 |
| hexa | the milestone is limited to the nixpkgs repository, which isn't great to start with | 23:46:58 |
| hexa | projects on the org level span multiple repositories which is more realistic for release engineering | 23:47:18 |
| 20 Mar 2022 |
 jonringer | In reply to @janne.hess:helsinki-systems.de
Does anyone know the purpose of the 22.05 milestone? It seems kind of redundant to the org-wide project to me. Or is there something nice about it I haven't noticed yet? we also wanted a way to track things across different repos: homepage, nixos-org-configuration, nixpkgs, etc | 00:34:26 |
| hexa | basically what I said, no? | 02:26:36 |
| jonringer | Yea, I read the question, answered it, then read your answer 😅 | 03:32:59 |
| Janne Heß | So the milestone is redundant and I don't have to care about it in my process? I'm also trying to write stuff like this down into the wiki so the next generations know what to do with it | 09:46:02 |
|  stigo joined the room. | 13:05:50 |
| jonringer | In reply to @janne.hess:helsinki-systems.de
So the milestone is redundant and I don't have to care about it in my process? I'm also trying to write stuff like this down into the wiki so the next generations know what to do with it I've stopped using it as a tool. Lots of little things made their way in with no one to do the work. So they're meaningless | 16:22:07 |
| 21 Mar 2022 |
|  nixinator joined the room. | 17:09:36 |
|  John Ericson joined the room. | 17:20:36 |
| 22 Mar 2022 |
|  Fabian Affolter joined the room. | 19:46:28 |
| 23 Mar 2022 |
| hexa | https://github.com/NixOS/nixpkgs/pull/161146 | 02:33:29 |
| hexa |
./alias/maintainers/scripts/remove-old-aliases.py --file ./pkgs/top-level/aliases.nix --year 2019 --month 6
| 02:33:35 |
| hexa | this feels like something that should be done once every release and a release manager entry could be helpful | 02:33:58 |
| hexa | * this feels like something that should be done once every release and a release manager entry could be helpful to make sure it happens | 02:34:03 |
| jonringer | Agreed | 04:34:39 |
| hexa | * this feels like something that should be done once every release and a release manager wiki entry could be helpful to make sure it happens | 04:36:57 |
