Thanks for the clarification I started in on some bugs that have not had any activity since 2017 and some from 2016 if I don’t hear back I’ll close them and advise if this is still a valid issue to reopen.
I did have one dev actually close their own bug after I pointed out to them there hasn’t been any activity in a while on it. My aim is to keep the tracker as clean as possible to allow you guys to focus on the tickets that matter. Sent from my iPhone > On 29 Jul 2018, at 07:18, Carsten Haitzler (The Rasterman) > <ras...@rasterman.com> wrote: > > On Sat, 28 Jul 2018 09:03:11 +0000 jaquil...@eagleeyet.net said: > >> Hi Guys, >> >> I think a good place for me to start as I fight with getting things >> built on fedora from git is that of traging of bugs that have had no >> activity for an extended period of time. I am posting a comment on them >> to see if I get any feedback and if there is no feed back I will mark a >> note on it for those subscribed to reopen the ticket if its still valid. >> >> Also I am seeing alot of bug reports of very low quality. In the sense >> there isnt any detail as to what the issue is. Is there a work flow that >> we can setup to ensure a standard of bug reports is met in the sense >> what steps we can take to try and reproduce as well as maybe hardware >> specs. >> >> I am sending this more to open up a discussion on this as i feel like >> phab should be used to help us report issues that developers can then >> try to reproduce and if replicated fixed. > > well TBH there isn't much you can do about what reporters will report. you ask > questions. often it's hard to get the information (people are unable to > provide > it - too complicated to get a backtrace for example - packages with no debug > symbols etc.). sometimes the backtrace is useless. (dies inside libc malloc > sanity checks - bug happened elsewhere and would need valgrind to know more). > sp it's often a conversation digging out more information. if that > conversation > stops (without a resolution or a "this needs to be handled later" from > developers), the bug basically becomes useless. : ( > >> Regards, >> Jonathan. >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> enlightenment-devel mailing list >> enlightenment-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> > > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > Carsten Haitzler - ras...@rasterman.com > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
