| 23 May 2024 |
 Vladimír Čunát | For illustration, let me paste a bit of timestamped log from channel activation (these aren't visible publicly):
May 22 22:13:48 pluto update-nixos-unstable-start[50857]: downloading /nix/store/in1gg39qhphlxj9ryd4k2mqdr7dy5j9j-nixos-plasma6-24.05pre629726.5710852ba686-aarch64-linux.iso/iso/nixos-plasma6-24.05pre629726.5710852ba686-aarc>
May 22 22:13:48 pluto update-nixos-unstable-start[50857]: $ NIX_REMOTE=s3://nix-cache nix --experimental-features nix-command store cat '/nix/store/in1gg39qhphlxj9ryd4k2mqdr7dy5j9j-nixos-plasma6-24.05pre629726.5710852ba686->
May 22 22:16:35 pluto update-nixos-unstable-start[50857]: downloading /nix/store/qawl76aqcm61vgms1vf8kfm0l21ay6lq-nixos-plasma6-24.05pre629726.5710852ba686-x86_64-linux.iso/iso/nixos-plasma6-24.05pre629726.5710852ba686-x86_6>
May 22 22:16:35 pluto update-nixos-unstable-start[50857]: $ NIX_REMOTE=s3://nix-cache nix --experimental-features nix-command store cat '/nix/store/qawl76aqcm61vgms1vf8kfm0l21ay6lq-nixos-plasma6-24.05pre629726.5710852ba686->
May 22 22:19:46 pluto update-nixos-unstable-start[50857]: downloading /nix/store/4n8bm9qqllfsi35gmbzxwjsf0f7di405-nixos-gnome-24.05pre629726.5710852ba686-aarch64-linux.iso/iso/nixos-gnome-24.05pre629726.5710852ba686-aarch64->
May 22 22:19:46 pluto update-nixos-unstable-start[50857]: $ NIX_REMOTE=s3://nix-cache nix --experimental-features nix-command store cat '/nix/store/4n8bm9qqllfsi35gmbzxwjsf0f7di405-nixos-gnome-24.05pre629726.5710852ba686-aa>
May 22 22:22:03 pluto update-nixos-unstable-start[50857]: downloading /nix/store/5kff34rypj8nkhcaan2bpvscmmxfw9j9-nixos-gnome-24.05pre629726.5710852ba686-x86_64-linux.iso/iso/nixos-gnome-24.05pre629726.5710852ba686-x86_64-li>
May 22 22:22:03 pluto update-nixos-unstable-start[50857]: $ NIX_REMOTE=s3://nix-cache nix --experimental-features nix-command store cat '/nix/store/5kff34rypj8nkhcaan2bpvscmmxfw9j9-nixos-gnome-24.05pre629726.5710852ba686-x8>
May 22 22:24:38 pluto update-nixos-unstable-start[50857]: downloading /nix/store/0zfg4fw0y7wwd5sz6yi3m93zc3h1mxsg-nixos-ova-24.05pre629726.5710852ba686-x86_64-linux/nixos-24.05pre629726.5710852ba686-x86_64-linux.ova to /home>
May 22 22:24:38 pluto update-nixos-unstable-start[50857]: $ NIX_REMOTE=s3://nix-cache nix --experimental-features nix-command store cat '/nix/store/0zfg4fw0y7wwd5sz6yi3m93zc3h1mxsg-nixos-ova-24.05pre629726.5710852ba686-x86_>
| 06:29:02 |
| Vladimír Čunát | All the three 24.05 channels are there. | 14:37:52 |
| Vladimír Čunát | So I guess this will come soon: https://nixos.github.io/release-wiki/Branch-Off.html#once-the-channel-is-available | 14:38:25 |
| Vladimír Čunát | Oh, looking at it, only the step (1) is missing, I think. | 14:40:20 |
 pbsds | 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 |
| pbsds | * 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 |
 raitobezarius | just after branch-off | 21:13:46 |
| raitobezarius | tagging the release happens on a parallel branch | 21:13:51 |
| pbsds | but this the week of backports. maintaining similarity between master and release-24.05 may be considered benefitial | 21:14:54 |
| pbsds | i commonly see comitters skip waiting for ofborg builds on backport during this week | 21:16:25 |
| pbsds | * i commonly see committers skip waiting for ofborg builds on backport during this week | 21:16:32 |
| pbsds | * i commonly see committers skip waiting for ofborg builds on backports during this week | 21:16:41 |
| raitobezarius | In reply to @pederbs:pvv.ntnu.no
i commonly see committers skip waiting for ofborg builds on backports during this week ?????????? | 21:18:25 |
 Lily Foster | In reply to @pederbs:pvv.ntnu.no
but this the week of backports. maintaining similarity between master and release-24.05 may be considered benefitial similarity yeah. RMs can better say/change when breaking changes are unrestricted. it should probably be clarified in release wiki though (and posted schedules) | 21:18:26 |
| raitobezarius | skipping ofborg builds is not acceptable under any circumstance | 21:18:38 |
| Lily Foster | In reply to @pederbs:pvv.ntnu.no
i commonly see comitters skip waiting for ofborg builds on backport during this week (this is a huge problem that needs to be addressed then) | 21:18:39 |
| raitobezarius | a backport is already a quite involved action | 21:18:46 |
| raitobezarius | skipping their CI is really unacceptable without a proper provided rationale before the merge or something | 21:19:02 |
| Lily Foster | In reply to @raitobezarius:matrix.org
skipping ofborg builds is not acceptable under any circumstance (well skipping eval checks at least. builds can be separately verified) | 21:19:09 |
| Lily Foster | (which i wouldn't clarify except that the aarch64-darwin build queue exists......) | 21:19:31 |
| raitobezarius | In reply to @pederbs:pvv.ntnu.no
but this the week of backports. maintaining similarity between master and release-24.05 may be considered benefitial i don't understand why this is the week of backports | 21:19:44 |
| raitobezarius | this is a bugfixing sequence at most | 21:19:50 |
| raitobezarius | not a "oops i missed the train, let me add my shit" sequence | 21:19:59 |
| Lily Foster | (yeah backports do continue for next 7 months too) | 21:20:05 |
| raitobezarius | so keeping similarity is not a goal afaik | 21:20:23 |
| raitobezarius | master should move on and do its things | 21:20:29 |
| raitobezarius | release-24.05 may continue to obtain some specific bugfixes during the beta phase as the testing uncovers some of them | 21:20:46 |
| raitobezarius | and manual conflict resolution can take place | 21:20:52 |
| pbsds | i looked through is:pull is:closed base:release-24.05, the ones i remember ofborg still building when merged have since completed. Quite a few PRs however never saw ofborg kick in | 21:27:36 |
| pbsds | This would've been solved by a merge wueue | 21:32:25 |
