Originally Posted By: Jim Fogle
I don't know if PG Music has changed their procedures but it use to be considered normal for the program update notification to lag behind one update.

The explanation I remember is this allows PG Music to remove the current build release if a severe issue is found soon after the build is released. This kind of situation is rare but it has happened.

Yes, they still do that. Now that I re-read Roger's message I understand what he's saying, and that's exactly the case there.
I work here