Comodo needs to implement a bug tracking mechanism.
Common ones they could use.
They can introduce another section within it for wishlist tracking.
This will allow all of us to identify the bug status and will allow Mod’s, User’s and especially Egemen and his team to have a more structured approach rather than having to trawl through huge lists of forum topics.
Melih / Egemen apologies if you have already been down this road.
Yes, reported bugs need to be tracked and the forums are not really a good vehicle for that. It’s
fine if bugs are reported in the forums, but once bugs are verified, they should end up in a tracking system so they will not be forgotten and hopefully fixed someday.
I agree. And Flyspray is one of the best I have used. It’s very small in code, very fast, and does want you want it to do without the hideous bloat of bugzillia.
The website is here: http://flyspray.org/
That would be the ideal situation. My impression is there seems to be resistance from within, for reasons unknown to me, to free up the resources to handle this. IMO, one/some of the dev(s) has/have all the strings in his/her/their hands and is/are spread to thin to find the time for such a tedious and sometimes ungrateful task. You really need people involved in the maintenance of the product to handle the bug tracking/fixing side of it. I wish I had an answer to make it better.
(At risk of flogging a dead horse) how about this.
(sincerely hope one of the Internal Comodo team reads this and posts feedback)
We need not depend on one dev owning the reins, we could work it at it from a community angle using the beta testing board members. I am sure many of us would be okay to support the entire activity, including moving posts from the board into the tracking system.
Since the Internal testing team already do the QA they could spearhead the activity of ensuring the internal stages of the defect cycle.
So that will leave the dev’s to only accepting, rejecting and marking as fixed.