Practise the standard verbs for coordinating a scheduled release train.
0 / 5 completed
1 / 5
Fill in: 'We ___ the next release train well before the cutoff, since a feature that misses the scheduled slot simply waits for the next one rather than forcing a special exception.'
We 'board a train' — the standard, simple collocation for getting a change included in a scheduled release cycle. The other options are less idiomatic here.
2 / 5
Fill in: 'Making exceptions for every late feature that asks nicely can ___ the whole release schedule sliding by days every single cycle, defeating the point of a fixed train.'
We say frequent exceptions will 'leave' the schedule sliding constantly — the standard, natural collocation for the resulting drift. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a release entirely if a serious defect surfaces close to the cutoff, since shipping on schedule is never actually worth shipping something known to be broken.'
We 'hold a release' — the standard, simple collocation for pausing a scheduled deployment when a serious issue appears. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every change into the train through the same review gate, so a rushed feature doesn't quietly bypass checks a normal one would have to pass.'
We 'merge a change' — the standard, simple collocation for including a piece of work into a shared release branch. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the departure date publicly well ahead of time, so every team knows exactly when their window to include a change actually closes.'
We 'announce a date' — the standard, simple collocation for publicly communicating a fixed schedule. The other options aren't idiomatic here.