[Elecraft] Tracking Elecraft Feature Requests

[Don Wilhelm]

I agree with Kevin's "Why"
Tell me of another amateur radio manufacturer who maintains such a list. 
  This is *not* open source programming.
If such a list exists for any other amateur radio manufacturer, they 
would come out with an "improved" new radio (Mark VI) version and if you 
wanted the "upgrade" you would have to buy the new radio.

With Elecraft, you get those "upgrades" at no cost, just download the 
firmware. You knew (or should have known) the capabilities of the radio 
when you bought it - you did review the specializations and features 
before you purchased it, did you not?

I don't think we need to have visibility into the Elecraft engineering 
resources, and prioritization of requests for added functions.

Those at Elecraft *do* listen and often respond to such customer 
requests, but the prioritization of those requests must be on Elecraft's 
terms for reasons of availability of engineering resources and the sales 
benefit of those changes.

Bug reports will get a different response than those requests for 
changed operation.  If bug reports are proven valid and repeatable, they 
will be attended to promptly.

73,
Don W3FPR

On 2/16/2017 7:54 PM, Kevin wrote:
> Why?
>
>
> On 2/14/2017 10:56 AM, Joe Stone (KF5WBO) wrote:
>> [js] It's important that we have visibility not only into features in the
>> pipeline, but also proposed features which have been rejected.
>>