Bob,
I can assure you that each released 'beta' firmware version has received
testing by the Firmware Test Team, and we are *not* the programmers.
Often times we are looking at a specific function that has been added,
but we also try to ring out the normal operation of the radio as well
(regression testing).
Sometimes we miss, and the residual problems are not discovered until
the firmware is released to 'beta' status. When the problems discovered
by the users of the 'beta' release are solved, the firmware is released
as a 'public' release.
Now, consider that those problems identified by those trying out the
beta version and being worked at the same time as the new and added
functions are being worked by the Firmware Test Team, the result is that
there are few 'public' releases at this time. The newest firmware with
the latest fixes as well as new function are to be found in the 'beta'
releases.
Sorry, but it is a situation of limited resources doing the best we can
to provide you with the 'latest and the greatest'. In time, the new
functions should diminish, and you will see more fixes in the firmware
releases. Right now, the concentration seems to be on enhancing the
sub-receiver functions. Be patient, the comments from general users
are not being ignored, but they may not be mainstream at this time.
73,
Don W3FPR
BOB PHILBROOK wrote:
I don't know to what extent or to what degree the tests of K3 firmware and DSP
upgrades must reach before being released for general use.
However, it is apparent to me with the numerous issues with NR and DSP that
more needs to be done before K3 software products are released for general use.
While I have no aversion to software upgrades, one does not want to trade one
set of problems for others. This, unfortunately, appears to be happening more
and more as the software becomes more extensive in capabilities.
I don't know if Elecraft utilizes such techniques, but independent verification and validation (IV&V) of software has proven time and time again to work. One cannot expect a software developer to adequately test his work.
Independent testing by a third party against approved criteria catches many
bugs and problems developers fail to see. And unless one has a rigorous,
structured software testing effort, problems such as those with DSP and NR will
come back and bite you every time. Having software tested by the developer
often leads to the old problem of two steps forward and one in reverse with
software releases.
I make the suggestion that more time be spent proofing firmware and DSP upgrades
and for Elecraft to employ software IV&V.
Bob, K9PAG
_______________________________________________
Elecraft mailing list
Post to: Elecraft@mailman.qth.net
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.138 / Virus Database: 270.6.7/1631 - Release Date: 8/24/2008 12:15 PM
_______________________________________________
Elecraft mailing list
Post to: Elecraft@mailman.qth.net
You must be a subscriber to post to the list.
Subscriber Info (Addr. Change, sub, unsub etc.):
http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/subscribers.htm
Elecraft web page: http://www.elecraft.com
