Exploits on github? A little organizing would be better?
Posted: Fri Feb 06, 2015 9:13 pm
What is your standing regarding posting exploits with STR on the bug tracker? On one hand it probably would make it easier for the developer to reproduce it if needed, but on the other hand you open a can of worms by making it public until it is fixed.
Also I see no one, or at least not on the past hundred or more issues, is tagging issues with labels, sorting them to be assigned. What is the purpose of the bug tracker then if bugs are not properly entered or assigned? I was told "developers know of this issue", but by filling a proper bug report on it, you can be sure it is tracked and fixed eventually if it's forgotten.
Check an example from TrinityCore, a World of Warcraft emulator project:
https://github.com/TrinityCore/TrinityCore/issues
Shiny tags or labels? Yes. Formatted issues? Yes. Even proposed fixes, but that's an open-source emulator.
I have worked in the game industry for a while in QA, and the internal databases (mostly Hansoft, Jira or Devtrack) require bugs to be filled following a ruleset, with expected behaviour, observed behaviour, reproduction rate, steps-to-reproduce and other parameters that help the developers find and fix whatever is needed. Can something like this, I mean not strict, but guidelines on posting bugs be put up for people?
Also, what DO you want exactly to be filed? I have no idea what the focus of the project is about now, but I'm sure you have areas you focus on, so focused testing and bug reporting could be implemented somehow as well? Like in the last Update, with Guilds, pets and morale, people could flock and bug them, then developers can easily track & fix.
Anyhow, I'll be submitting my bug reports in the meanwhile as I come across them.
Raelion/sebid
Also I see no one, or at least not on the past hundred or more issues, is tagging issues with labels, sorting them to be assigned. What is the purpose of the bug tracker then if bugs are not properly entered or assigned? I was told "developers know of this issue", but by filling a proper bug report on it, you can be sure it is tracked and fixed eventually if it's forgotten.
Check an example from TrinityCore, a World of Warcraft emulator project:
https://github.com/TrinityCore/TrinityCore/issues
Shiny tags or labels? Yes. Formatted issues? Yes. Even proposed fixes, but that's an open-source emulator.
I have worked in the game industry for a while in QA, and the internal databases (mostly Hansoft, Jira or Devtrack) require bugs to be filled following a ruleset, with expected behaviour, observed behaviour, reproduction rate, steps-to-reproduce and other parameters that help the developers find and fix whatever is needed. Can something like this, I mean not strict, but guidelines on posting bugs be put up for people?
Also, what DO you want exactly to be filed? I have no idea what the focus of the project is about now, but I'm sure you have areas you focus on, so focused testing and bug reporting could be implemented somehow as well? Like in the last Update, with Guilds, pets and morale, people could flock and bug them, then developers can easily track & fix.
Anyhow, I'll be submitting my bug reports in the meanwhile as I come across them.
Raelion/sebid