Geek Answers Handbook

Should I keep to-do lists in source control?

I have some problems finding the best way to store todo lists for programming.

I consider the following:

  • one todo list in the source control for each project
  • master todo list (with common tasks) in a personal folder in the source control

How did you find this?

What would you suggest?

Edit:

Thanks for the suggestions. I use the bug tracking system (BugTracker.NET) for errors and tasks that are related to other people's requests so that they can see the status. And I use // TODO in the code.

I have many additional notes on what to do. Would you also recommend putting this in an error tracker (especially if it's impossible to specify them as // TODO in the code)?

+5
12

?

: Bugzilla Mantis Trac

...

+14

. . , .

Doxygen. :

// TODO: fix potential non-assigment of var
int my_var;

Doxygen ( , FIXME BUG LOOK_HERE ..) a) todo / b) todos .

, todos todo- , ( ) .

, : Doxygen, scm- ( ) bugzilla .

. git hook, Github TODO

, TODO , Good Thing (TM): .

+5

- .

- Todo, RtM.

, // TODO "" , IDE , .

+4

TODO, . , , //TODO: , , , .

, - !

. ?:) TODO .

, grep ( ).

.

TODO.

+2

TFS, . , , ..

+1

, . , ( ), -commit- .

.

+1

, . ( , ) .

0

OnTime2008, ( 5 ) . . , "todo", , , , !

0
0

Basecamp HQ

, .

.

0

Eclipse ( Java) , TODOS:

  • , , ()
  • use several keywords, which means different things for your team (for example, FIXME may be urgent with high priority, EXTEND may be a future opportunity for expansion with low priority, etc.).
0
source

More articles:


All Articles