| 12 Feb 2022 |
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 |
hexa | https://docs.google.com/spreadsheets/d/13MJqF6S6avO7G8w21dgCZR-jtVJxuZTlo9H4UF45mU8/edit?usp=sharing | 00:40:52 |
jonringer | While we are stable channels, I created a hacky script to delete merged backports:
git remote prune origin; git branch -r --merged release-21.11 | grep origin | grep backport | sed -e 's|/| |' | sed -e 's| ||' | xargs -l bash -c 'git push -d $0 $1'
| 01:43:56 |
jonringer | also, mother fucker... thursday we were at ~2900 open PRs, now were back up to 3100 | 01:47:31 |
jonringer | I really need to get basinix finished... | 01:47:45 |
hexa | Yeah, the flood of PRs is ever more slightly getting out of hand | 01:50:03 |
hexa | In my gut feeling it matches the projected growth for 21.11 | 01:50:34 |
hexa | Thursday I saw PR id 158800, today 159600 | 01:52:12 |
hexa | Or whatever 4 days ago was | 01:52:31 |
hexa | Over 200 PRs per day | 01:53:07 |
jonringer | https://monitoring.nixos.org/grafana/d/v-86aB-Zz/github-issues-and-prs?orgId=1&viewPanel=10&from=1644522152631&to=1644717244758 😠| 01:54:54 |
hexa | 1010 PRs merged this week. https://github.com/NixOS/nixpkgs/pulse | 02:02:21 |
hexa | that page does not scale to our usage 😕 | 02:02:42 |
jonringer | lol, it usually errors for me when I do the monthly pulse | 02:03:28 |
jonringer | When I first got a commit bit, I think we did close to those number each month | 02:04:01 |
jonringer | hmmm, maybe more like 1500 / month | 02:04:18 |
jonringer | but still, that's 4x in ~2 years | 02:04:24 |