Open Adimote opened 1 year ago
What was the motivation for this?
I know that we had an issue where the knockouts were due to start at the wrong time, but I'm not aware of any similar issues around the league matches for SR2023.
In SR2023 we decided on the Saturday to move the league matches half an hour later, which could have been caught earlier. In a previous year I recall our discovering late that the league matches did not fit into the allotted time.
It also might have prompted our discussing moving the time of the group photo earlier.
In SR2023 we decided on the Saturday to move the league matches half an hour later
Whur? I don't recall this.
You and I sat at the scoring table, I passed on from a team that they wanted to get to the venue a little later due to marathon faff and breakfast times. We looked at the timings, you worked out how long a spare we had for the Sunday morning, and we then rescheduled the Sunday morning block half an hour later.
Commit: https://github.com/srobo/sr2023-comp/commit/d6e7c3fa65e1cc361886271b09f4e226e988c2dd
You and I sat at the scoring table, I passed on from a team that they wanted to get to the venue a little later due to marathon faff and breakfast times. We looked at the timings, you worked out how long a spare we had for the Sunday morning, and we then rescheduled the Sunday morning block half an hour later.
Commit: srobo/sr2023-comp@d6e7c3f
Huh, I'd forgotten about that.
I'm not sure that that fits the description of this task though? The description here implies that this is about catching errors due to mismatches in the schedule, rather than deliberately choosing to change the schedule at some point. (Hence my question about whether this is meant to be about the knockouts; see https://github.com/srobo/sr2023-comp/commit/c59d172f8204149c12f3736fb3d64c9b08604533)
Add last minute schedule check to the process (Runbook/Recurring tasks), against srcomp, and league match timings and count