The Second CUMming

As you know, my company recently scheduled the February CUM Release. As with most CUM releases, it was scheduled for Saturday and, like most scheduled CUM releases, it did not go (or CUM) as planned.

I have already received six (update: seven, no, wait, now eight) additional e-mails on the February CUM Release. The first indicated that CUM Release was extended until Sunday at 9pm. Think about baseball. Think about baseball.

Next were "unexpected issues during installation of the February CUM Release". My source tells me that this was a software issue but, not to worry, these things happen to everyone from time to time. The release was delayed until 11pm. Then 1am. Think about baseball. Think about baseball.

By around 4am, they had the whole team working on the CUM release. Normally, the preferred team size is two people for a CUM release although one-person teams are used more frequently than people admit. Many people fantasize about being in a three-person CUM release but, in reality, the third person just ends up watching and forming their own one-person team. The CUM release was now delayed until 6am.

This is getting serious. I have heard that possible side-effects of delaying a CUM release like this could include cancer or at a minimum, some things turning blue.

Good news! At 6am, they apparently had completed the CUM release because they were testing the "ERP" function. If they can get the ERP validated, they may try a snowball after that but that is not the way you want to end a CUM release.

It is now 10am Monday and they have closed the Oracle that the CUM release was installed in. They announced that "If you lose your session [wink, wink] you should [put your] log back into [the] Oracle and you will be directed to an instance that is active." Now that is talent!