[go-nuts] What's up with the 603 TODO/todo comments in the common go code?

edit: bad copy paste. cd /usr/local/go;grep --exclude=*.o -rnw . -e "todo"
-e "TODO" should do it. No need for the double "todo" :)

I'm not sure what you're asking. TODOs mark things that are yet to be
done, either because people haven't had the time or knowledge to do
them, or aren't in a hurry to do them. They're perfectly normal in
large code bases.

I suppose I had thought that TODOs in a complex project would be contained
in something like github issues or some other issue/feature tracking thing,
rather than lying around in code.

However, I'm pretty new to code bases of this size, so I wouldn't know
either way. Just seemed odd.

Maybe a better question would be, "How do the go dev folks keep track of
issues/features outside of TODOs, and how do they correlate their (tickets,
github issues, etc) to the TODO sitting in code?"

Jean

There's a separate issue tracking system that's part of the code review
process. It's not as "ad-hoc" as it looks.

The issues list is here: https://code.google.com/p/go/issues/list

The code reviews take place on this
platform: https://codereview.appspot.com/all

There are Google groups for development (
https://groups.google.com/forum/#!forum/golang-dev ) and code reviews (
https://groups.google.com/forum/#!forum/golang-codereviews ) as well.


Cheers,

Silvan

Thank you, this makes more sense.

Jean