GB 2.0 were probably pissed at GB 1.0 for setting an end date that would fall in GB 2.0's reigning period. They've passed on the problem to GB 3.0, who will in turn pass it on to GB 4.0 and on and on it goes.
They still want a close enough carrot on a stick to keep the rank and file malluable - but want it far enough away so they will be dead by the time the org needs another date shift. They just want a quiet and comfortable run in their old age.