[Elecraft] K3 4.81 beta anomally

[Lynn W. Taylor, WB6UUT]

I've conducted many beta test cycles over the past couple of decades.  I 
have software in beta now.

Part of my beta test agreement states that "Beta software is broken.  
Your job is to help find the problems so they can be fixed before 
production."

More than a few times I've withdrawn functions and features because they 
didn't prove to be useful, sometimes spectacularly so.

It's pretty common for a beta test agreement to include a non-disclosure 
clause.

Particularly now, with the internet, bugs can develop a life of their 
own, even if they're never present in released software.

I don't know what Elecraft does, but software released for beta testing 
is reasonably subject to the terms and conditions that Elecraft chooses 
-- and as widely or narrowly as they wish.

Bugs found in testing have practically no bearing on ones' investment -- 
except perhaps as a distraction.  I'd argue that a wide-open beta 
actually reduces the value of your investment.

73 -- Lynn

On 2/8/2014 3:57 PM, Don Wilhelm wrote:
> Beta releases are intended to allow those who are willing to be early 
> testers of new firmware to participate in evaluating that new level.  
> If there are no significant problems, that level may be advanced to 
> production, but if there are problems discovered, that firmware level 
> will never 'see the light of day' other than the beta version.