Sure. Maybe it wasn't supposed to "roll-out" but it's quite obvious they are "testing" something on that dataset.
Otherwise, why have it exist?
I don't necessarily buy that argument, but it's plausible.
It still begs the questions I posed to Matt.
It begs the question, "What the heck is going on at the 'plex that this has happened twice now?"
Sorry, but in GIVING Goog credit for KNOWING what they are doing, it gives away alot of valuable information that they wouldn't want webmasters to reverse-engineer
If they DON'T know what they are doing, then.. umm.. hello. <begin and end Google Noise rant here>
So I'm left with 2 arguments. The first makes more sense in MY mind.
It's a case of "Ignore the man behind the curtains".
At this point, it doesn't matter too much to me.
The "bug" gave me more than enough info to use advantageously.
I hope others think carefully and logically about the hows and whys of this event and make their own conclusions.