Release Management | 340 Members | |
| 25.11 "Xantusia" | https://nixos.github.io/release-wiki/Home.html | 93 Servers |
| Sender | Message | Time |
|---|---|---|
| 22 May 2024 | ||
| done | 21:19:18 | |
| where is k900 | 21:19:27 | |
| ok | 21:19:28 | |
| if anyone want to take the commit bit from me for those two projects, glad to get rid of them | 21:19:52 | |
https://github.com/NixOS/amis/pull/132 is ready to merge once the tested job is green | 21:38:21 | |
wondering if I should gate uploads on https://hydra.nixos.org/jobset/nixos/release-24.05-small instead of https://hydra.nixos.org/jobset/nixos/release-24.05 ? thoughts? | 21:42:39 | |
I guess it doesn't matter that much given I'm only uploading the AMIs weekly and not for every bump. release-24.05 sounds fine. | 21:44:25 | |
| 23 May 2024 | ||
| Would it be possible to add the Currently the AMI upload script is having the image on releases.nixos.org would make the script a lot faster and waste a lot less bandwidth | 06:13:05 | |
| * Would it be possible to add the Currently the AMI upload script is having the image on releases.nixos.org would make the script a lot faster and waste a lot less bandwidth | 06:14:10 | |
| On the other hand it would make channels update slower and naturally we'd also pay for the storage. | 06:17:13 | |
| in what way would make it the channel update slower? amazonImage is already part of the tested job | 06:18:58 | |
| Redacted or Malformed Event | 06:19:48 | |
| 24.05 boots successfully on Amazon 🥳 https://github.com/NixOS/amis/actions/runs/9203089651/job/25314015902?pr=132 | 06:22:53 | |
| Redacted or Malformed Event | 06:23:48 | |
In reply to @arianvp:matrix.orgThe update process needs to download the image from cache and upload it to the bucket. | 06:25:45 | |
In reply to @arianvp:matrix.org* The update process needs to download the image from S3 and upload it to the bucket. | 06:26:07 | |
| Gotcha. So we just move the slowness to somewhere else. Okay. I'll just keep it like this for now | 06:26:08 | |
| * The update process needs to download the image from S3 and upload it to the other bucket. | 06:26:14 | |
| For illustration, let me paste a bit of timestamped log from channel activation (these aren't visible publicly):
| 06:29:02 | |
| All the three 24.05 channels are there. | 14:37:52 | |
| So I guess this will come soon: https://nixos.github.io/release-wiki/Branch-Off.html#once-the-channel-is-available | 14:38:25 | |
| Oh, looking at it, only the step (1) is missing, I think. | 14:40:20 | |
| it seems the release schedule does not detail when breaking changes are unrestricted on master. Should than be after branch-off, or after tagging the release? | 21:12:45 | |
| * it seems the release schedule does not detail when breaking changes are unrestricted on master. Should this be after branch-off, or after tagging the release? | 21:13:02 | |
| just after branch-off | 21:13:46 | |
| tagging the release happens on a parallel branch | 21:13:51 | |
| but this the week of backports. maintaining similarity between master and release-24.05 may be considered benefitial | 21:14:54 | |
| i commonly see comitters skip waiting for ofborg builds on backport during this week | 21:16:25 | |
| * i commonly see committers skip waiting for ofborg builds on backport during this week | 21:16:32 | |
| * i commonly see committers skip waiting for ofborg builds on backports during this week | 21:16:41 | |