| 10 May 2024 |
 ma27 | so I just realized that postgresql12 will be EOL on nov 14 which is within the supported range of 24.05. opinions on removing/keeping it? we're past the breaking change restriction of may 1 already.
also am I right with my interpretation of https://github.com/NixOS/nixpkgs/issues/303285 that current staging will be merged into staging-next and that's the second staging cycle for 24.05? asking for a few postgresql updates. | 09:10:05 |
 hexa | we have on staging cycle remaining before branch-off | 09:13:55 |
| hexa | * we have one staging cycle remaining before branch-off | 09:14:00 |
| hexa | and I'm pro removal of postgresql12 🙂 | 09:14:39 |
 Alyssa Ross | oh right — do package removals count as breaking changes? I have a couple I've been holding off on merging because I wasn't sure. | 09:49:13 |
 vcunat | I'd say they do, at least if the packages worked, etc. (there will be some gray cases surely) | 09:51:54 |
 Weijia | I guess yes, but I won't block them if they're considered pre-release cleanups. | 09:52:33 |
| Weijia | https://nixos.github.io/release-wiki/Feature-Freeze-Announcement.html#pre-release-cleanup | 09:52:52 |
| Alyssa Ross | aha okay | 09:53:21 |
| Alyssa Ross | I'm thinking of https://github.com/NixOS/nixpkgs/pull/308820 and https://github.com/NixOS/nixpkgs/pull/310170, so I guess both of those would be fine? | 09:53:44 |
| Weijia | Yeah | 09:54:48 |
| hexa | thunderbird 102 is a big security nono 🙂 | 15:58:47 |
| hexa | we can't keep it around | 15:58:54 |
| hexa | the alternative would be to mark it vulnerable and remove it post branchoff | 15:59:25 |
| Alyssa Ross | it's been marked vulnerable since september IIRC | 16:02:22 |
| Alyssa Ross | i.e. we forgot to remove it after the last branch-off | 16:03:02 |
| 12 May 2024 |
|  NixOS Moderation Bot unbanned  @timdeh:matrix.org. | 17:09:18 |
| 13 May 2024 |
| vcunat | Hydra queue looks like today or tomorrow we'd be able to start a new staging-next iteration. Schedule says that in two days we should start the last staging-next iteration (the last one reaching 24.05 at least). | 16:38:02 |
| vcunat | Given that it's the last one, it has impact on workflow of people who merge PRs. So, how would you like to proceed? Move the date one day earlier? Or just delay by one day? (Well, I could trigger build now and on Wednesday merge the new staging state again, hoping that it won't invalidate much of the builds.) | 16:39:45 |
| vcunat | * Given that it's the last one, it has impact on workflow of people who merge PRs. So, how would you like to proceed? Move the date one day earlier? Or just make Hydra wait one day? (Well, I could trigger build now and on Wednesday merge the new staging state again, hoping that it won't invalidate much of the builds.) | 16:40:11 |
| Weijia | In reply to @vcunat:matrix.org
Given that it's the last one, it has impact on workflow of people who merge PRs. So, how would you like to proceed? Move the date one day earlier? Or just make Hydra wait one day? (Well, I could trigger build now and on Wednesday merge the new staging state again, hoping that it won't invalidate much of the builds.) I prefer what's between the parentheses | 16:56:00 |
| Weijia | What about you, Mic92? | 16:58:27 |
 Mic92 | Looks like we don't have too much stuff left queued staging that is zhf related? https://github.com/NixOS/nixpkgs/pulls?q=is%3Aopen+is%3Apr+label%3A%2210.rebuild-linux%3A+5001%2B%22 | 17:05:28 |
| Mic92 | But I also think we can trigger now and than merge stuff on Wednesday if there is important things in there. | 17:06:00 |
