Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Need help to triage github bug tracker
#1
Hello Guys,

I need your help to triage the github issue tracker. We have tons of issue, so far 236. If an issue takes 1 week to be fixed, I let's you count how many years will be necessary to reduce this number Wink

What need to be done
* Close duplicate report (if you're not sure just add a note)
* Close useless/invalid bug report (if you're not sure just add a note)
* Add tags. Most of you don't have the right to add them so I propose to add them in the comment zone. Later a poor uy that got permission will report them back to github
* test some issues that may have been fixed with recent change/PR (yeah keep dreaming gregory!)
* any useful thing that could help to sanitize the situation

What need to be discussed
* What to do for bug fixed in openGL ? Keep them open, or just close them. Honestly I don't expect anyone to update the DX9/DX11 renderer.

Your contribution will be gladly appreciated
Reply

Sponsored links

#2
(04-26-2016, 02:03 PM)gregory Wrote: * What to do for bug fixed in openGL ? Keep them open, or just close them. Honestly I don't expect anyone to update the DX9/DX11 renderer.

I still think it'd be better to have the issue open and just add a label mentioning "Fixed in OpenGL".

Gabest did say that he might look into D3D12 if he moves to Windows 10. It would be useful to keep track of D3D11 bugs just in case they're essential as an referable information for developers. Also refraction did port some of the texture shuffling code to D3D11.

Also I don't think you need to keep track of D3D9 issues (it's awfully outdated).  Just the ones with D3D11 should be enough I guess...
Reply
#3
None of the bug testers have permissions to add tags or close issues on github.
[Image: gmYzFII.png]
[Image: dvedn3-5.png]
Reply
#4
(04-26-2016, 03:13 PM)Nobbs66 Wrote: None of the bug testers have permissions to add tags or close issues on github.

TBH FlatOut is the only bug squad member actively testing/reporting stuffs at the moment. If there are any plans for providing permission on GIT then I really think he is the only one who deserves it. Smile

On the other hand, I think the reason we have lack of testers is due to the fact that testing/bug reporting isn't as much as appreciated as coding.
Reply
#5
(04-26-2016, 03:01 PM)ssakash Wrote: I still think it'd be better to have the issue open and just add a label mentioning "Fixed in OpenGL".

Gabest did say that he might look into D3D12 if he moves to Windows 10. It would be useful to keep track of D3D11 bugs just in case they're essential as an referable information for developers. Also refraction did port some of the texture shuffling code to D3D11.

Also I don't think you need to keep track of D3D9 issues (it's awfully outdated).  Just the ones with D3D11 should be enough I guess...

You seem to imply that a new renderer will have the same issue as an old renderer. Some bugs are due to unimplemented feature therefore not real "bug". Information are still available as closed bug report, you can still filter the tag too. Texture shuffling is potentially broken (was just a copy/past 1 year ago) and Ref is very happy with openGL.


(04-26-2016, 03:13 PM)Nobbs66 Wrote: None of the bug testers have permissions to add tags or close issues on github.

(04-26-2016, 03:35 PM)ssakash Wrote: TBH FlatOut is the only bug squad member actively testing/reporting stuffs at the moment. If there are any plans for providing permission on GIT then I really think he is the only one who deserves it. Smile

Here my proposal
* If you are an active bug squad member, and you want tag/close "power", PM me and I will give you contributor right access on github. I will limit access to few people to avoid git issue but not because I don't trust you.
* otherwise you can still leave a note on the tracker. And another guy (to not say I) will do the tracker update.

Quote:On the other hand,  I think the reason we have lack of testers is due to the fact that testing/bug reporting isn't as much as appreciated as coding.
I probably don't say it enough. But without all testers (of 1 day, or active for years), nothing would have been possible on GSdx. It is really a team work. And honestly we misses dev too Wink
Reply
#6
(04-26-2016, 03:35 PM)ssakash Wrote: On the other hand,  I think the reason we have lack of testers is due to the fact that testing/bug reporting isn't as much as appreciated as coding.
And the testing, especially posting compatibility reports on the forum isn't very user friendly at the moment.
There are currently two reports in the request thread, one made by me almost 3 months ago, which haven't be created or otherwise responded to. I recently searched for a game on the forum, got one result, a decent report from the same request thread from 2014, which wasn't created either. Many (especially PAL)games don't have threads there, so wannabe testers who want to share their results can't create a thread themselves, and see older reports left for dead in the request thread. I doubt that has a possitive effect on their motivation. The wiki receives many more compatibility/issue reports because they can be posted for any game without a hassle, but you lose out on some of the details they might've shared in a report on the forum.
Reply
#7
Hum, wiki+ github + forum. It feels like too much place to report bug.
Reply
#8
(04-26-2016, 04:11 PM)gregory Wrote: You seem to imply that a new renderer will have the same issue as an old renderer.

Usually when writing code for a new renderer it's natural to assume that the certain coder will code using the older renderer as a reference to replicate the same functional behaviour and only after that he might focus on unimplememted features.

In such cases , the bug reports will help fix issues on the new renderer. Either way,  I'm fine with it if closed issues could be still be sorted based on tags.

Quote:Here my proposal
* If you are an active bug squad member, and you want tag/close "power", PM me and I will give you contributor right access on github. I will limit access to few people to avoid git issue but not because I don't trust you.
* otherwise you can still leave a note on the tracker. And another guy (to not say I) will do the tracker update.

Sounds good to me. This might be useful to indicate the importance/value of testing. Smile
Reply
#9
Maybe we can prevent future clutter by having users make a proper thread in the Bug Reporting subforum instead of Github.
  • Github would be reserved to certain people, devs/bug squad members. 
  • Basically devs would post a few issues with the relative forum URL - and this represents what is currently being worked on.
  • This would prevent alot of the duplicate issues between the forums and Github we currently have.
[Image: 36a66c559937a1f5d0cd7460362d4093.jpg?bg=2c2c2c]
Reply
#10
(04-26-2016, 04:33 PM)gregory Wrote: Hum, wiki+ github + forum. It feels like too much place to report bug.

Not to mention that the Wiki is outdated quite a bit with a majority of the issues still on there. It gets updated when it gets spotted, but the Forum is honestly more active when it comes to bugs and the status on them.
Intel Core i5-4670K @ 3.40GHz | 16GB (2x8GB) DDR3-1866 G.SKILL Sniper Series
AMD Radeon R9 280 @ 3 GB | 120GB SSD | Windows 7 Ultimate x64 (SP1)
Reply




Users browsing this thread: 1 Guest(s)