| 25 Jan 2022 |
 jonringer | ius: do you mind posting this over on "nixos marketing", the nixos homepage is more their domain | 17:49:48 |
 ius | Great, was unaware - done | 17:58:20 |
| 30 Jan 2022 |
|  Janne Heß left the room. | 13:18:40 |
| 31 Jan 2022 |
 hexa | can someone create 22.05 blockers on the org level please? | 21:43:18 |
| hexa | I'd like to create issues for package removals that need to be addressed in time | 21:43:32 |
| jonringer | I cc'd domen in dev channel | 21:44:37 |
| hexa | maybe something to add to the todo? to create that for the next release so everyone can queue stuff | 21:47:26 |
| hexa | * maybe something to add to the docs? to create that for the next release so everyone can queue stuff | 21:47:38 |
| jonringer | Yea, I'll add it to the release wiki | 21:48:24 |
| 1 Feb 2022 |
|  Domen Kožar joined the room. | 10:04:41 |
| 2 Feb 2022 |
|  tristan joined the room. | 20:28:32 |
| hexa | https://github.com/NixOS/nixos-org-configurations/pull/201 | 22:18:12 |
| hexa | old release status deprecation needs to be added to the release documentation maybe? | 22:18:28 |
| jonringer | https://github.com/NixOS/release-wiki/pull/29 | 23:04:57 |
| 5 Feb 2022 |
| jonringer | Any objections to https://github.com/NixOS/nixpkgs/pull/156355? otherwise I think I will clean it up, rebase, then merge it. It should be an improvement over what we had before | 03:19:25 |
| 12 Feb 2022 |
| jonringer | tomberek: nrdxp Not sure when you two want to do the next call for release manager, but I would probably put the call out now. ZHF for 22.05 will be starting in ~10 weeks. | 19:18:01 |
 tomberek | It's crossed my mind too. Plus there are stability issues with new kernels and things like https://github.com/NixOS/nixpkgs/pull/155054 cropping up. | 19:26:35 |
| hexa | still no 22.05 blockers project 😢 | 19:52:45 |
| hexa | I wish the org owners would just set up a room where they track requests | 20:53:50 |
| hexa | or set up any other way to request stuff | 20:54:17 |
| hexa | and interesting observation regarding the number of merged stable backports:
- 19.03: 301
- 19.09: 377
- 20.03: 609
- 20.09: 943
- 21.05: 1291
- 21.11: 892
We're 75 days (35%) into the current release
There are 137 days until its EOL.
Linear projection: 892 * (212/75) ~= 2.5k
| 23:43:45 |
| hexa | I'm sure it will not come to this, the backports will very probably be slowing down later in the release cycle | 23:44:28 |
| hexa | * and interesting observation regarding the number of merged stable backports:
- 19.03: 301
- 19.09: 377
- 20.03: 609
- 20.09: 943
- 21.05: 1291
- 21.11: 892 (so far)
We're 75 days (35%) into the current release
There are 137 days until its EOL.
Linear projection: 892 * (212/75) ~= 2.5k
| 23:44:56 |
| hexa | Pretty sure this is a direct result of the backport action. | 23:47:16 |
| hexa | It was introduced on 2021-05-24 | 23:47:35 |
| hexa | Also 151 PRs tagged security in 75 days is pretty much two per day | 23:49:45 |
| 13 Feb 2022 |
| hexa | oh and I only looked at the base:release-XX.YY, so I probably undercounted (missing at least base:staging-XX.YY and base:staging-next-XX.YY for newer release) | 00:00:43 |
| tomberek | Do you think our policy allows too much backports? I mean, if you backport every single thing, it's equivalent to staying on unstable. | 00:37:35 |
| hexa | hard to say from numbers alone | 00:38:25 |
| hexa | I think we have rejected a number of stable backports, because we didn't see the reason to have them | 00:38:55 |
