On Thu, 2008-02-21 at 17:42 +0000, Jim wrote:
> The md5sum on our end is pretty important, actually: we *want* to know
> when the content changes, and then not work until it's QA'd to not cause
> major problems.
That's fine for development releases, but once the stable release has
been made, you've got your users to think about. This should _not_ be a
fatal error. Toss a popup if you must, but leaving the user high and dry
with respect to flash _every time Macromedia makes a new release_ is
really bad.
What's been really problematic is that the issues have been found in the
latest release of flash affect a small number of users (and has taken a
long time to resolve), but the package prevents all users from
installing it.
On Thu, 2008-02-21 at 17:42 +0000, Jim wrote:
> The md5sum on our end is pretty important, actually: we *want* to know
> when the content changes, and then not work until it's QA'd to not cause
> major problems.
That's fine for development releases, but once the stable release has
been made, you've got your users to think about. This should _not_ be a
fatal error. Toss a popup if you must, but leaving the user high and dry
with respect to flash _every time Macromedia makes a new release_ is
really bad.
What's been really problematic is that the issues have been found in the
latest release of flash affect a small number of users (and has taken a
long time to resolve), but the package prevents all users from
installing it.