Then it's probably just Verizon checking and re-checking and re-re-checking and ... Which is better than releasing a new version and having it brick 90% of the phones that get it. I'd rather get it right than get it soon. (And, as an old developer [starting back in the late 60s], I know how some tiny little bug can be a lot more difficult to fix than something huge.)
TMobile, for example, once pulled an update after the release was announced - the night before it went live. And it took them a couple of weeks, IIRC, to find and fix the bug someone had found.
If the phone is easy to flash, you can always flash back to the old version if the update soft-bricks the phone - but if it damages the - in Samsung's case - download partition, you're dead, and they have to start replacing millions of phones. (At least with an unlockable bootloader, you stand a chance of just booting the boot image and getting everything back, if you didn't back up before accepting the update.)