In a post that does nothing to allay my concern over the increasing silence (does that even make sense?) regarding Leopard, Jacqui Cheng of Infinite Loop makes the case that Leopard will in fact be delayed. Pointing to the input of various sources, but more importantly, the patterns of Apple’s behavior during previous OS releases, Jacqui makes the case that the current builds of Leopard are just too darn unstable to consider a release possible in the imminent sense:
Is it possible that Apple is keeping some of its key developers in the dark by holding back a surprise, nearly-perfect build? Sure. Anything is possible. But seems like just about the worst idea ever if the company wants anyone’s software to work when Leopard comes out. This is not super-insider information either, say our sources. “Anybody who has really worked with a Tiger or Panther seed will know the same stuff.”She also shares one more “surprise” about Leopard:
One more tip we got regarding Leopard, is that InputManager plugins are no longer allowed. That’s right… no more little hacks from anybody besides Apple. No more Apple menu hacks. No more Safari plugins. (InputManager is not exactly the same as APE, by the way.) “Apple isn’t really broken up about it since InputManagers were often used for nefarious purposes anyway,” our sources said, but the loss of InputManager control will break a lot of shareware and commercial software that currently makes use of that control.
A June release wouldn't be out of line with Apple's schedule...a spring release gives them until June 20. Of course, most of us would rather see an early spring release...but they still have plenty of time.
June is not a delay. Just because you wanted it earlier doesn't mean Apple is obliged to hold to your overly optimistic assumptions regarding a Spring release.