Earth to customer - ryandesign
Yes. It's a normal and accepted software-development practice to fix not just one but a number of problems before releasing a new version. Releasing too many updates too frequently has the effect that customers do not download every version. Allowing a little time to pass between fixing a problem and releasing the version with this fix also enables internal testing to discover possible problems with the fix. This is better than releasing a possibly-broken fix immediately and annoying customers with the resulting problems.It's unfair to say that Snapz Pro has been broken for a month. It continues to work perfectly fine on 10.3.x, and the developer never said it worked on 10.4.x (until 2.0.2, which is now available). You have the responsibility to verify that all your software is compatible with a new operating system release before you install that new operating system. Failure to do so is nobody's fault but your own.
Wednesday, June 01 2005 @ 01:43 AM PDT
- Earth to customer - frdfr | Thursday, June 02 2005 @ 06:05 PM PDT
Earth to ambrosia ? - Twistyfaster
Have installed 2.0.2, <em>still</em> no audio with Tiger.Wednesday, June 01 2005 @ 09:33 AM PDT
- Earth to ambrosia ? - Oscar F. Hills, MD | Friday, June 03 2005 @ 08:52 AM PDT
Earth to customer - ryandesign
Yes. It's a normal and accepted software-development practice to fix not just one but a number of problems before releasing a new version. Releasing too many updates too frequently has the effect that customers do not download every version. Allowing a little time to pass between fixing a problem and releasing the version with this fix also enables internal testing to discover possible problems with the fix. This is better than releasing a possibly-broken fix immediately and annoying customers with the resulting problems.It's unfair to say that Snapz Pro has been broken for a month. It continues to work perfectly fine on 10.3.x, and the developer never said it worked on 10.4.x (until 2.0.2, which is now available). You have the responsibility to verify that all your software is compatible with a new operating system release before you install that new operating system. Failure to do so is nobody's fault but your own.
Reply to This
Wednesday, June 01 2005 @ 01:37 AM PDT