| 20 Nov 2023 |
figsoda | In reply to @raitobezarius:matrix.org figsoda: Can you reconvene a time for the next branch-off attempt? The same time (7pm UTC) works for me | 20:19:13 |
raitobezarius | In reply to @infinisil:matrix.org From what you told me though, the workflow in https://github.com/NixOS/release-wiki/pull/70 seems to be working though. It only doesn't work because of a mistake, which wasn't documented before. I already explained that this workflow is not equivalent to the previous one due to the absence of signing | 20:19:35 |
raitobezarius | (+ the tag) | 20:20:11 |
raitobezarius | Whether or not this works is not really relevant, being mistakes resilient or mistake undoable is also important for a workflow | 20:20:27 |
raitobezarius | There's an infinite amount of workflows that could work | 20:20:40 |
raitobezarius | But there's one we adopted before and new ones we could adopt and we didn't really adopt new ones because this one is not merged | 20:20:56 |
raitobezarius | * But there's one we adopted before and new ones we could adopt and we didn't really adopt this new one because this one is not merged | 20:22:01 |
infinisil | At least we can see now what works and what doesn't, it's kind of hard to test this otherwise. | 20:22:43 |
raitobezarius | Either case, I hope this opportunity will enable us to be a bit more mindful about this type of situation because I kind of warned about those scenarios where things don't really behave as expected and this would create setbacks for ceremonial processes like branch-off | 20:23:16 |
infinisil | I do hope that we don't end up in a situation where the branch protection settings need manual updates every release though | 20:23:33 |
raitobezarius | It's a shame that we wasted the time of people who came for the branch-off process but anyway I am not a GitHub organization owner so I cannot unblock this. | 20:23:40 |