| 6 Dec 2025 |
 hexa | off by 6 months, sorry | 00:06:48 |
| hexa | * off by 6 months, sorryo say | 00:06:50 |
| hexa | * off by 6 months, sorry to say | 00:06:51 |
 Vladimír Čunát | I ended up at least starting it without reviewing the open pull requests (except those marked as security) | 00:06:53 |
| Vladimír Čunát | * New staging-next-25.11: https://github.com/NixOS/nixpkgs/pull/468267 | 00:07:05 |
| Vladimír Čunát | Corrected now. | 00:07:24 |
| Vladimír Čunát | I hope I didn't forget any other place. I was just manually replacing 25.05 to 25.11 in the whole text. | 00:07:46 |
| Vladimír Čunát | I suppose we'll still get a go update in there within a day or two. | 00:08:42 |
 mdaniels5757 | Already in (unless there's going to be another): 25.11-next contains https://github.com/NixOS/nixpkgs/pull/467315 | 02:09:37 |
 whispers (it/fae) | hi! i just opened a pr with an update to libgit2 (https://github.com/NixOS/nixpkgs/pull/468449), and am unsure if this needs to be targeted at master, staging, or staging-nixos. CONTRIBUTING.md says <500 rebuilds is fine for master, but CI also gave it 10.rebuild-nixos-tests. does that mean I should retarget to staging? | 15:34:31 |
| whispers (it/fae) | * hi! i just opened a pr with an update to libgit2 (https://github.com/NixOS/nixpkgs/pull/468449), and am unsure if this needs to be targeted at master, staging, or staging-nixos. CONTRIBUTING.md says <500 rebuilds is fine for master, but CI also gave it 10.rebuild-nixos-tests. does that mean I should retarget to staging? (this may also be the wrong matrix room, unsure where to ask) | 15:35:06 |
 K900 | staging-nixos | 15:36:10 |
| whispers (it/fae) | * hi! i just opened a pr with an update to libgit2 (https://github.com/NixOS/nixpkgs/pull/468449), and am unsure if this needs to be targeted at master, staging, or staging-nixos. CONTRIBUTING.md says <500 rebuilds is fine for master, but CI also gave it 10.rebuild-nixos-tests. does that mean I should retarget to staging-nixos? (this may also be the wrong matrix room, unsure where to ask) | 15:44:07 |
| whispers (it/fae) | thanks! | 15:56:09 |
| 7 Dec 2025 |
|  Alex Epelde joined the room. | 18:35:11 |
| Alex Epelde left the room. | 18:37:13 |
| Alex Epelde joined the room. | 18:37:26 |
|  Robert Evans joined the room. | 18:46:49 |
| Robert Evans set a profile picture. | 19:02:49 |
| 8 Dec 2025 |
|  @hhr2020:mozilla.org joined the room. | 01:53:07 |
| @hhr2020:mozilla.org left the room. | 01:53:49 |
|  raboof joined the room. | 15:46:37 |
| raboof | https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#staging describes staging is 'regularly' merged into staging-next. I'm curious what the 'criteria' for that are - I suppose you generally don't pull in more changes from staging when staging-next is close to be mergable to master? | 16:05:07 |
 emily | we do not pull in any until it merges | 16:05:57 |
| emily | (unless we have to) | 16:06:03 |
| emily | staging-next is there so that rebuilds sent to staging don't throw away builds in the cycle | 16:06:31 |
| emily | (or we'd have to "freeze" staging periodically which AIUI was done in the old days) | 16:07:05 |
 Grimmauld (any/all) | only viable if the preople running staging can reasonably keep track of all open mass rebuild PRs, those days are long over | 16:07:59 |
| raboof | right so essentially only when staging-next merges into master, staging becomes the 'new staging-next'? | 16:08:29 |
| emily | I get the impression it was more yelling at people for merging into staging at the wrong time | 16:08:32 |
