Comments on: Apple Delays Mac OS X 10.5.7, Continues Development [Seed Notes]

By: yakyakyak.fr - La communauté des utilisateurs de Final Cut Studio » Blog Archive » 10.5.7 arrive, les bugs s’en vont ! (màj)

Wed, 13 May 2009 06:10:12 +0000

[...] Comprend d’autres améliorations relatives à la fiabilité et à la stabilité de l’impression. Attention : des utilisateurs de Mac Mini ont déjà signalé que la mise à jour peut entraîner des problèmes de reconnaissance de certains moniteurs DVI dont la résolution réelle ne serait plus reconnue. Plus de détail sur les changements dans la note de mise à jour de la béta (en anglais). [...]

By: Erscheint Mac OS X 10.5.7 schon am Freitag? » Software News

Erscheint Mac OS X 10.5.7 schon am Freitag? » Software News — Thu, 07 May 2009 06:49:30 +0000

[...] Build 9J58 war für die Entwickler die bislang letzte Beta-Version, in der man sich insbesondere um die [...]

By: Mac OS X 10.5.7 erscheint angeblich am Freitag - Software | News | ZDNet.de

Wed, 06 May 2009 10:05:15 +0000

[...] hatten vergangene Woche mit Build 9J58 die bislang letzte Betaversion erhalten, die vor allem Probleme mit iChat und Safari beseitigt. Der [...]

By: И все же обновлению Mac OS X 10.5.7 на этой неделе быть? | Macs.in.ua: Программы для Mac OS X

Mon, 04 May 2009 15:55:16 +0000

[...] Если же говорить про апдейт в целом, то он охватывает практически все области Mac OS X, а общее число исправлений превышает сотню. Собственно, это и объясняет то нетерпение, с которым он ожидается. С самым полным перечнем текущих изменений можно ознакомиться здесь. [...]

By: bogg

bogg — Mon, 04 May 2009 06:53:37 +0000

pheh said:Superhero:
Apple confirmed the problem and decided on releasing the fix in 10.5.7.

Still no evidence that the problem really is in OS X itself. It could just as well be Apples way of saying “Sorry, didn’t think anyone used that function/API-call/whatever” or maybe Apple just found it easier to work around the problem in OS X instead of asking X number of developers to fix their applications?

I know what I’d do if I were Apple…

I want to put the blame on Canon, Nikon etc. because of one single reason:

They had “all the time in the world” to try their applications in the 10.5.6 beta seeds and report the problems… Did they?

By: pheh

pheh — Sun, 03 May 2009 20:57:56 +0000

Superhero:

If you took a couple of minutes to research the issue, Apple has confirmed that this was their fault and that the fix will be in 10.5.7.

Never will I be surprised at the fervent “It can’t possibly be Apples fault ever.” from people that can’t even take a moment of their time to make sure they have any clue as to what they are talking about.

10.5.6 developers made the change that broke the software;

Canon, Nikon, and a couple of other vendors researched the issue (after much haranguing) and told Apple about it;

Apple confirmed the problem and decided on releasing the fix in 10.5.7.

How much money were you betting again?

By: superhero

superhero — Sun, 03 May 2009 08:57:53 +0000

pheh said:

…

The issue lies somewhere in the “Image Capture Extension” or within an associate library, and it also effects the stability of portions of the Nikon software.

…

I wonder if more could have been done. I took me almost 3 weeks to get Canon to even acknowledge the issue. Did Canon or Nikon lean on Apple for this fix? Could either or both companies have thrown some money at Apple for a quicker fix?

Why not Ask Canon/Nikon to lean on their own developers and get them to fix it in Their application instead?
If two _THIRD PARTY_ applications gets unstable after an upgrade, shouldn’t the responsibility lie on the third party developer to get it stable again and not Apple?

I’m betting money on that both Canon and Nikon are using some undocumented or not recommended API:s or similar and Apple just patched those in 10.5.6

Just my two cents…

By: Sammelsurium: Mac OS X 10.5.7 Build 9J58, verfrühte Radeon 4870, iPhone-Zufriedenheit, MobileMe-Aussetzer, etc.

Sun, 03 May 2009 06:20:09 +0000

[...] weitere kleinere Fehlerbehebungen stecken in Mac OS X 10.5.7 Build 9J58 – die jüngste Fassung wird Entwicklern inzwischen zum Test angeboten. Weiterhin führt Apple nur [...]

By: celtikmind

celtikmind — Sat, 02 May 2009 13:11:45 +0000

Maybe… they should untie their hands?

That way they could actually release it some d**n time!

By: Yet Another Build of Mac OS X 10.5.7 Has Been Seeded | Mactropolis.com - Your Friendly Global Mac Community

Sat, 02 May 2009 03:22:12 +0000

[...] In the seemingly never-ending stream of builds for the point update that will never get here, comes another build. This build (9J58) has only two areas of change, both affecting CFNetwork in association with Safari, VPN and iChat, according to World of Apple. [...]

By: Mac OS X 10.5.7 beta 9J58… Y retraso. « Apple’s Blog ™

Mac OS X 10.5.7 beta 9J58… Y retraso. « Apple’s Blog ™ — Fri, 01 May 2009 20:12:27 +0000

[...] Enlace |Apple Delays Mac OS X 10.5.7, Continues Development [Seed Notes] [...]

By: BradMacPro

BradMacPro — Fri, 01 May 2009 16:15:11 +0000

If the upgrade kit for older Macs to use the ATI Radeon 4870 HD requires a driver only found in 10.5.7, then what kind of driver is used on the 2009 Mac Pro that optionally comes with this card? Also to reply to the above comment from pheh about Canon and Nikon having issues with Mac OS 10.5.6, then that sounds like they need to fix their software, not Apple, unless the problem is with a (Apple) admitted fault in Apple’s programming.

By: Apple delays OS 10.5.7 | FairerPlatform.com

Apple delays OS 10.5.7 | FairerPlatform.com — Fri, 01 May 2009 15:15:21 +0000

[...] to World of Apple, which offers a full listing of OS X 10.5.7 changes to date, Safari 4 Beta browser will not [...]

By: pheh

pheh — Fri, 01 May 2009 13:29:02 +0000

Must… vent… now…

Okay great, they want to get it right, I appreciate that. Meanwhile since November I’ve been reporting to Apple and Canon that their 10.5.6 update killed the stability of the “EOS Utility”. The issue lies somewhere in the “Image Capture Extension” or within an associate library, and it also effects the stability of portions of the Nikon software.

Now, some six months later there is still no fix. The “solution”: forgo any patching for security and stability made in 10.5.6 and revert to 10.5.5 – for six months. Even though we aren’t talking about a core critical system, somewhere someone within Apple made the decision not to dedicate any time into releasing a fix for any higher end camera users until the release of 10.5.7.

I wonder if more could have been done. I took me almost 3 weeks to get Canon to even acknowledge the issue. Did Canon or Nikon lean on Apple for this fix? Could either or both companies have thrown some money at Apple for a quicker fix?

Lest any fanbois feel put out over this “diatribe”. Take this comment for what it is: A personal need to occasionally feel like my frustration is documented somewhere when I otherwise feel powerless in working toward a solution.