How about a web page only for bugs?
Could be put in the Help menu "Known Bugs/Issues" and doesn't require a new
release to keep current. A section for each release would be appropriate
showing "Fixed" status too.
Users would eventually learn to check that first avoiding most of the repeat
questions on the list.
de Mike W9MDB
On Friday, November 23, 2018, 9:10:00 AM CST, Richard Zwirko - K1HTV
<[email protected]> wrote:
Tom, Regarding your comments about the release notes, if fact almost all of
the issues that I addressed as examples are NOT covered in the latest released
notes.
I do like your idea of having to go to another page to read the list of known
issues (and then possibly having to check a box?) before being able to
download the latest RC version.
As far as maintenance of the list, it would take far less time for developers
like Joe, Bill(s), Mike, etc. to add a new known RC issue to the list than
having to compose separate replies to users, as is being done now.
73,Rich - K1HTV
= = =
From: Richard Zwirko - K1HTV <[email protected]>
To: "G4WJS, Bill" <[email protected]>, WSJT
<[email protected]>
Cc:
Bcc:
Date: Fri, 23 Nov 2018 04:01:04 -0500
Subject: [wsjt-devel] Post a "Know Issues" list?
Bill, et al,Wouldn't it be a good idea to post a list of known WSJT-X issues on
a regular basis? We all see SO MANY repeat posts complaining about problems
being experienced with release candidates. Hopefully, posting such a list would
greatly reduce repeat problem complaints.
Some known issues could include:> Colors for stations worked/needed, etc aren't
working.> Poor RC4 sensitivity (Not a problem, RC4 can't copy 75 bit signals)>
Why the error message about LOTW and how to fix it (Win32 Open SSL)> Not
running split and wondering why stations don't copy TX tones above 2500 HZ.>
Etc, etc.
73,Rich - K1HTV
---------- Forwarded message ----------
From: Tom Melvin <[email protected]>
To: WSJT software development <[email protected]>
Cc:
Bcc:
Date: Fri, 23 Nov 2018 10:38:20 +0000
Subject: Re: [wsjt-devel] Post a "Know Issues" list?
Do you think that would help 90% of the posters - sorry I don’t think so.
The 77 bit signal and LOTW errors are very clearly mentioned in the release
notes - which everyone is advised to read but don't
Those looking at the mailing lists - there is an archive/search option - even
just reading what was in last few hours in some cases would show the answer.
Posting a list - while many people will get a nice warm feeling of things
actually happening esp on some of the more obscure issues but don’t think will
affect the number of similar queries.
Many people do not understand the concept of beta tests - they think it is just
another upgrade, jump in with both feet and are surprised when there is a
slight issue, panic, scream and start reloading old versions and wasting so
much of their time in the process where a 1 mins check of the dreaded … Release
Notes - would have answered it.
Human nature is not to RTFM no getting away from it - posting a list of
known/fixed issues would be great to refer people to but won’t cut down
repetitive questions.
73’s
Tom - GM8MJV
P.S. What may help is on the download page you have to go via another page of
‘issues’ before being able to download but that would take maintenance and the
dev teams have better things to do.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
