Apple seeds Mac OS X 10.6.1 Snow Leopard to developers

“Just six days after the release of Mac OS X Snow Leopard to the general public, Apple has begun extensive testing of the first update amongst the developer community,” Alex Brooks reports for World of Apple.

MacDailyNews Take: As expected. Apple released Mac OS X 10.5 Leopard on October 26, 2007 and quickly followed with 10.5.1 developer seed on November 6, 2007 and 10.5.1 general release on November 15, 2007. Mac OS X 10.4 Tiger was released on April 29, 2005 and 10.4.1 was released on May 16, 2005.

Brooks continues, “Build 10B503 (a significant step from the shipping 10A403) weighs in at a meagre 71.5MB and features just a handful of changes, affecting connectivity issues with 3G modems, difficulty removing items from the Dock and unresponsive copies of Motion 4.”

MacDailyNews Note: Our shipping version of Mac OS X 10.6 is Build 10A432.

Full article, with seed notes, here.

15 Comments

  1. Saying it’s just 6 days is a little misleading as that implies that they only finished it on the day of release. I know the final build wasn’t that long before release, but once you add that time to however long they then test 10.6.1 it won’t be that short of a time. As it is they make it sound like the thing totally wasn’t ready.

  2. 10.6 has been a disaster for my MacBook Pro, so I hope 10.6.1 fixes more than cosmetic stuff.

    Since the upgrade, Safari, Firefox, Camino and Opera browsers all crash on uploading of anything connected with acrobat or jpg files. I spent 1.5 hours with an Apple SL engineer yesterday fixing problems. As a web to print software trainer my whole day practically was screwed.

    Word of caution: watch out for start-up items [remove them ALL]; be wary of browser plugins — safaripdfviewer.plugin brought my Snow Leopard system to its knees.

    Everything would crash. From Skype, InDesign [CS4], Acrobat 6 Pro and Acrobat 9 Pro, TextEdit and all the browsers mentioned above.

    After the engineer fixed the glaring problem [ie. a $3000 doorstop], I’m still getting InDesign crashes. I feel seriously burned — and somewhat bitter — by being an early adopter of 10.6.

    Never again.

  3. ONe way of avoiding update problems is to never add any “plug ins” or “haxies” or “enhancements” that mess or change in any way your apple apps and core system functions …(menu, widgets, finder, etc .. etc..) Keep your machine lean and mean.

    a lot of problems are caused by these third party conflicts .. I’ve learned the hard way with a Safari plug in that renedered it useless for 3 months until I figured it out …

  4. So far, so good. My Nov 2007 iMac 24″ is more responsive and I have not yet run into a significant issue. I can’t even recall an insignificant issue right now. It may be a coincidence, but my Airport Extreme connectivity seems to be a lot more reliable, too. But I may have power-cycled it after installing SL.

  5. Seeding an update at this point makes perfect sense.

    Keep in mind that it took a few of weeks to press all the available copies of 10.6 Snow Leopard. The pre-order numbers were unprecedented. That means that a few weeks ago 10.6.0 was locked as ready for release. No way does a developer sit still while discs are being pressed. Apple have used those weeks to continue work on 10.6. It only ‘appears’ that they ‘rushed’ the 10.6.1 update.

  6. @HueyLong

    Similar things happened to me when I went from Tiger to Leopard. The moral of the story? I learned that I should disable and remove ANY AND ALL plugins for any application. I was a first-day adopter of Snow Leopard, and I’ve had zero problems. You don’t need to give up being an early adopter, just take some preventive measures. Remove all plugins (but keep a list of them!) and then check periodically to see if they’ve been updated for the latest release.

  7. Why doesn’t Apple provide a secure/supported path for 3rd party developers who create plug-ins (InputManagers) or haxies? Don’t understand why this is such a BFD.

Reader Feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.