Django migration fails "URL Tab doesn't close on stop" Sanity check? (user error) "Manual time doesn't work" Potter shenanigans waste a whole day Rick Hamilton finds a bug "This MR needs to be release, not master" Fixing TestLink spelling errors Rubin's VM explodes Shawn wall of text MR Ruby Crash "Michael, I'm assigning you the SAML test" "Did you clear your cache?" The release is late (we care) Long debate about dev cycle Support/sales engineer gives RC to customer "We can always make a sub- release" The release is late (we don't care) Dev pushes changes to wrong branch "Did you check the logs?" Dan Dalton finds a bug Last minute "emergency" issue Django migration fails "URL Tab doesn't close on stop" Sanity check? (user error) "Manual time doesn't work" Potter shenanigans waste a whole day Rick Hamilton finds a bug "This MR needs to be release, not master" Fixing TestLink spelling errors Rubin's VM explodes Shawn wall of text MR Ruby Crash "Michael, I'm assigning you the SAML test" "Did you clear your cache?" The release is late (we care) Long debate about dev cycle Support/sales engineer gives RC to customer "We can always make a sub- release" The release is late (we don't care) Dev pushes changes to wrong branch "Did you check the logs?" Dan Dalton finds a bug Last minute "emergency" issue
(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.
Django migration fails
"URL Tab doesn't close on stop"
Sanity check? (user error)
"Manual time doesn't work"
Potter shenanigans waste a whole day
Rick Hamilton finds a bug
"This MR needs to be release, not master"
Fixing TestLink spelling errors
Rubin's VM explodes
Shawn wall of text MR
Ruby Crash
"Michael, I'm assigning you the SAML test"
"Did you clear your cache?"
The release is late (we care)
Long debate about dev cycle
Support/sales engineer gives RC to customer
"We can always make a sub-release"
The release is late (we don't care)
Dev pushes changes to wrong branch
"Did you check the logs?"
Dan Dalton finds a bug
Last minute "emergency" issue