Welcome, Guest
Username: Password: Remember me

TOPIC: New BugReport System for V3 Alphas, please submit issues through that system

New BugReport System for V3 Alphas, please submit issues through that system 19 Nov 2021 15:09 #1

  • N8SDR
  • N8SDR's Avatar
  • OFFLINE
  • Posts: 623
  • Thank you received: 294
Incase you haven't looked at the latest Software release updates please note there is a new reporting system that should be used for V3 Alpha release Bug/issues and requests.

Using the system benefits all of us, as it makes it easier to track the bugs rather then induvial posting and emails, also it is easier for everyone to see if that bug/issue or request has already been submitted: copied and pasted below from the software V3 tab

NEW V3 Bug Reporting System and Rules:Please report bugs or issues you find in the ExpertSDR3 using the GitHub system. Doing that follow the rules below. github.com/ExpertSDR3/ExpertSDR3-BUG-TRACKER/issues
This is the short version of the rules, the full set of rules is published on GitHub.
1. Read the list of the current issues. Avoiding duplications is a very important goal, so please pay attention to what is already there. If you see the report, which is close, but not exactly what you want to report - good practice is to contact the author and confirm. It's better to add something to the existing report rather than create a new one.
2. Fill in the Title: please be short, descriptive, and informative. The Title is meant to be easily readable by everyone. Correct Title is a great deal to prevent duplications.
3. Fill in the "Write" section. Please remember that no one is expecting you to be perfect since the start, however, there is good practice to look at examples. We recommend you to use the following template:
* Device and serial number
* ExpertSDR3 version and build number
* OS: Windows 10/ macOS/ Linux Ubuntu - under which OS you have confirmed the issue
* Your PC parameters briefly.
* Description: full and most descriptive information about the bug/issue
* Correlations: indicate if you found any dependencies or conditions under which issue/bug occurs.
* Reproduction steps - describe if applicable
4. Please note that adding info to the existing report (as the report progress) is important. If you found new or corrective information - please submit it ASAP. As usual, please keep it short, but as much descriptive as possible.
Suggestions
If you'd like to suggest a new feature or have some ideas, which might improve ExpertSDR3, please share your thoughts with us using the GitHub system.
73 Rick
Last Edit: 19 Nov 2021 15:10 by N8SDR.
The administrator has disabled public write access.
The following user(s) said Thank You: S58WW, Rome, Tom_G0JSV

New BugReport System for V3 Alphas, please submit issues through that system 19 Nov 2021 19:59 #2

  • Tom_G0JSV
  • Tom_G0JSV's Avatar
  • OFFLINE
  • Posts: 74
  • Thank you received: 29
Thanks Rick

One obvious issue is that the GitHub bug tracker contains both Russian/English content so difficult to de-dupe. (re Point 1 below)

Just waiting for my auth code from Git to post a new feature but noticed you were online so a quick hello.

Tom
The administrator has disabled public write access.

New BugReport System for V3 Alphas, please submit issues through that system 19 Nov 2021 20:21 #3

  • N8SDR
  • N8SDR's Avatar
  • OFFLINE
  • Posts: 623
  • Thank you received: 294
Tom_G0JSV wrote:
Thanks Rick

One obvious issue is that the GitHub bug tracker contains both Russian/English content so difficult to de-dupe. (re Point 1 below)

Just waiting for my auth code from Git to post a new feature but noticed you were online so a quick hello.

Tom

Hello back at you

Yes that is true for use posting unless were fluent in both languages, but I would image it is much easier on the EE staff! instead of getting numerous emails , at least it will/should reduce most of that mess for them
73 Rick
Last Edit: 19 Nov 2021 20:22 by N8SDR.
The administrator has disabled public write access.

New BugReport System for V3 Alphas, please submit issues through that system 19 Nov 2021 20:39 #4

  • Tom_G0JSV
  • Tom_G0JSV's Avatar
  • OFFLINE
  • Posts: 74
  • Thank you received: 29
Rick,


OK, just received my GitHub auth code and posted a suggestion.

A few things were noticed. All commentary below is intended as constructive criticism.

1: The new feedback mechanism seems to be devoid of any structure. (Compared to the previous version) You suggest a template to fill out the form (the 'Write' section) but I suspect this will be ignored. (Ooops...guilty of that)

2: Personally I would like to be able to classify my issue as a bug, enhancement or other at the point when the issue is raised. (Even if it is later reclassified by the developers)
The administrator has disabled public write access.

New BugReport System for V3 Alphas, please submit issues through that system 19 Nov 2021 21:18 #5

  • N8SDR
  • N8SDR's Avatar
  • OFFLINE
  • Posts: 623
  • Thank you received: 294
Tom_G0JSV wrote:
Rick,
-

OK, just received my GitHub auth code and posted a suggestion.

A few things were noticed. All commentary below is intended as constructive criticism.

1: The new feedback mechanism seems to be devoid of any structure. (Compared to the previous version) You suggest a template to fill out the form (the 'Write' section) but I suspect this will be ignored. (Ooops...guilty of that)

2: Personally I would like to be able to classify my issue as a bug, enhancement or other at the point when the issue is raised. (Even if it is later reclassified by the developers)


I suspect there work on the gitHub aspect, - its new to them and will require a bit of tweaking and structure-
I just posted the comment that users should use it, since that was what was listed under the updated software tab and instructions-
73 Rick
Last Edit: 19 Nov 2021 21:19 by N8SDR.
The administrator has disabled public write access.

New BugReport System for V3 Alphas, please submit issues through that system 20 Nov 2021 00:00 #6

  • VK6NX
  • VK6NX's Avatar
  • OFFLINE
  • Posts: 327
  • Thank you received: 158
@Tom_G0JSV

Regarding 2 - Labels (github.com/ExpertSDR3/ExpertSDR3-BUG-TRACKER/labels) at this stage can be assigned by "advanced users". In practice it means that every submission still goes via initial evaluation by the EE's personnel, who is capable to define whether it is bug (or request, etc). Users (as yourself or myself) may be sure it is a bug - but is it really, or just unfinished implementation? EE can define, users cannot. That is why at this stage Labels are in EE hands only. Later, perhaps, EE will define whether they will grant advanced access to Testers. EE's Developers are currently directly involved and managing, and trying to access whether using of Github is actually worth it, or something else need to be used instead.

In a nut shell the Github mechanism is not targeted to ease of Tester's life :yes:. It is, actually, quite opposite BTW - it should make EE's dev team life easier, hence, they will build the structure, which will serve their purposes to define the bugs and progress with the fix. There are few options how it can be done by using Guthub; however which one to use - this is not entirely clear at this stage, and this is what can be defined by starting using Github's reporting.

Regarding 1. It is not implemented by Github. Labels/Projects/Milestones together should work (theoretically), but is it worth to lodge the time to structure it - that is currently unknown. We will see in next few weeks. What we have at this stage are:
- visibility to Developers and Testers of all submitted requests (ideally this should stop mailing flood to EE inbox and and allow EE to concentrate on evaluation)
- initial structure with Labels.

Regarding EN/RU. This is uncertain part at this stage. Dev team prefers RU, most of users are submitting in EN. Roman is a translation point. As first step to avoid duplication it was thought someone from "adv users" will keep RU submission filled with EN translations. We should see how (and if) it works.
The administrator has disabled public write access.
The following user(s) said Thank You: N8SDR

New BugReport System for V3 Alphas, please submit issues through that system 21 Nov 2021 01:26 #7

  • VK6NX
  • VK6NX's Avatar
  • OFFLINE
  • Posts: 327
  • Thank you received: 158
Actually... I really think it was bad idea to enable public access to Github tool :)
My feeling is - if we continue, the tool will turn very soon into flooded trash can where we all will be lost.
I also believe it is just waste of time trying to "push" people to do "right" reporting. We just need at this stage to use people, who know "how to report" it already.

Roman?

Example why: github.com/ExpertSDR3/ExpertSDR3-BUG-TRACKER/issues/68 (and there are few more like that). (@danweecc - nothing personal, I have left you few comments, hence, perhaps you will care to fix it).
The administrator has disabled public write access.

New BugReport System for V3 Alphas, please submit issues through that system 21 Nov 2021 01:34 #8

  • danielwee
  • danielwee's Avatar
  • OFFLINE
  • Posts: 209
  • Thank you received: 29
No worries - I have updated to furnish the information.
The administrator has disabled public write access.

New BugReport System for V3 Alphas, please submit issues through that system 21 Nov 2021 02:05 #9

  • VK6NX
  • VK6NX's Avatar
  • OFFLINE
  • Posts: 327
  • Thank you received: 158
Just for sake of more productive discussion and faster move into right direction.

The below link is unfinished documentation draft, which was proposed to Roman:
github.com/VK6NX/EE-Software-TestLounge---documentation/blob/main/README.md

It was intended for initial EE's review and adoption with necessary amendments, into EE's bug report portal. Obviously :D Roman is flooded with his common duties, that is why documentation review was not finished and ported as yet. At this stage I am a bit busy with my own projects and cannot keep "appropriate pressure" :rofl: on Roman, hence I just leave the proposed documentation open for discussion amongst potential Testers. I really hope it will not turn into flame and will move to everyone (EE and users) advantage.

Productive comments and suggestions are really appreciated.
The administrator has disabled public write access.
The following user(s) said Thank You: Rome

New BugReport System for V3 Alphas, please submit issues through that system 21 Nov 2021 02:16 #10

  • danielwee
  • danielwee's Avatar
  • OFFLINE
  • Posts: 209
  • Thank you received: 29
Having developed hardware with software support, I think at this stage having more feedback is better than less. Ideally the feedback contains all the necessary information but even when there isn't all the requisite information, the aggregation of multiple reports often help reveal underlying bugs or oversights. The thing is to let the developers address this in their own timing and sequence without insisting that it needs to be fixed "NOW". Such reports are invariably a bit messy for such a complex piece of software. Having a public feedback like this also serves to answer questions users might have, and prevent getting the same issues pointed out repeatedly - in the absence of ready documentation. From what I can see, there are only a small number of people giving feedback and unless you're getting loads of people actively looking for issues and testing out the features, I find the current system just fine.
The administrator has disabled public write access.

New BugReport System for V3 Alphas, please submit issues through that system 21 Nov 2021 14:18 #11

  • N8SDR
  • N8SDR's Avatar
  • OFFLINE
  • Posts: 623
  • Thank you received: 294
VK6NX wrote:
Just for sake of more productive discussion and faster move into right direction.

The below link is unfinished documentation draft, which was proposed to Roman:
github.com/VK6NX/EE-Software-TestLounge---documentation/blob/main/README.md

It was intended for initial EE's review and adoption with necessary amendments, into EE's bug report portal. Obviously :D Roman is flooded with his common duties, that is why documentation review was not finished and ported as yet. At this stage I am a bit busy with my own projects and cannot keep "appropriate pressure" :rofl: on Roman, hence I just leave the proposed documentation open for discussion amongst potential Testers. I really hope it will not turn into flame and will move to everyone (EE and users) advantage.

Productive comments and suggestions are really appreciated.

Looking that link over, makes sense to me, Sorry I would have not placed my feature request on the gitHUB, site, but it was contradicting at this point Since the EESDR Software Tab. Bug Report mentioned to use it for Features as well. so, if you wish please just delete those feature requests I have done via the new reporting system.

However, do you find issue with perhaps using the DISCUSSION tab for possible feature request- just a thought?

cheers
73 Rick
Last Edit: 21 Nov 2021 14:21 by N8SDR.
The administrator has disabled public write access.
The following user(s) said Thank You: Rome

New BugReport System for V3 Alphas, please submit issues through that system 21 Nov 2021 22:18 #12

  • VK6NX
  • VK6NX's Avatar
  • OFFLINE
  • Posts: 327
  • Thank you received: 158
Just to make it absolutely clear, how it works at this moment

Here below are official EE spaces:
https://github.com/ExpertSDR3/ExpertSDR3-SUGGESTIONS/issues = Feature requests, Enhancements, Documentation requests, etc
https://github.com/ExpertSDR3/ExpertSDR3-BUG-TRACKER = Bug reporting ONLY

and here below is "howto" documentation draft (for both above links) - kind of guidance how to submit bug reports and feature requests (very important - do not paste any bugs and suggestions in here, it is just documentation. Use above links instead) :
https://github.com/VK6NX/EE-Software-TestLounge---documentation#readme
Last Edit: 21 Nov 2021 22:19 by VK6NX.
The administrator has disabled public write access.
The following user(s) said Thank You: Rome
Time to create page: 0.106 seconds