[EAS] CAP, Text to Speech, and April 23

[Mike McCarthy]

It's not that simple. If the release involves a compulsory issue such as
suspending TTS, then it's a required update and the box needs to be
updated. Then comes along another compulsory update (IPAWS server
related.) Guess what, another update. Oh and this bug and that bug which
seems to impact my particular operation. It goes on and on.  I really pity
the first adopters.

While in theory and much practicality, it is our option to update the box.
In reality, there is no option many times due to the compulsory nature of
disparate organizations possessing great difficulty in having a dialog to
unify issues. So we all have the great pleasure of going to each installed
box twice in the coming month to update things TWICE.

And I expect another update before June 30 unless the box manufacturers
say otherwise.

MM

> Maybe it is just me, but it seems like people are making this more
> complicated than it needs to be.  This software update business boils down
> to the following key points:
>
> 1. Whether a particular vendor releases one software update or 20 in a
> given period of time, that vendor does NOT control how often WE engineers
> installs it!  As long as the vendor makes "Release Notes" readily
> available also, WE engineers can determine whether a particular update is
> worthy of our time and what priority to attach to it.

SNIP

>    IMHO, it is past time for SAGE to get out a software release that
> addresses the TTS issue, IPAWS, and MyStateUSA compatibility issues.
> If subsequent events lead to another software release.... see #1 above.
>
> Dave