View Single Post
  #2   Spotlight this post!  
Unread 02-01-2011, 16:14
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Bug tracking with Git

I'm certainly not going to try and talk you out of using a more task-oriented tool, but for small teams and somewhat short-lived projects, Excel or another spreadsheet program works pretty well for bug and feature tracking.

Do what you can to avoid conflicts, but it is pretty trivial to diff.

Make your initial set of column headers match the fields you care about, and perhaps use sheets for a major topic (programmer names, or features vs bugs). Another nice feature is the flexibility with which you can sort or chart.

Greg McKaskle