Issue Tracking

[ManicManiac64]

Hey everybody,

A couple of days ago during a team meeting, Mr. Amerman mentioned issue tracking and I think it'd be good idea to implement that so we can easily keep track of who's working on what within the repository. Just made this discussion to get others' thoughts on it.

-James

[sirfifer]

Especially since we are already plowing into this season, keeping it simple is likely key.

I think using GitHub's issues for both actual bugs and for defining features/changes to be worked will likely be a big help.

This system is much simpler than most issue trackers, that said, I think that using labels, projects, and milestones will help organize this work and set a target for a given fix/change/addition to be released.

In general, the most important info that every issue needs to be workable includes:

• Clear description of the actual issue
• Clear description of the environment, info on versions of libraries and code, platform, etc
• Clear details on how to to reliably reproduce the issue as that is the first thing someone needs to do when they start working on an issue.

That all said, keeping things simple is still always key.