My feeling is that if a TODO is so small that it's not worth raising a Github issue about it, then it's best to take some time to implement it in the original patch. If that is too much of a burden, then it's a good indication that it is not in fact a small task (and in that case, go ahead and create the issue).
On Mon, Oct 1, 2018 at 11:02 AM Roman Leventov <leven...@apache.org> wrote: > Druid project has a policy of creating issues on Github instead of TODOs in > code, but I feel that this is an overkill for small documentation-only > tasks. I suggest to allow TODOs that ask just for writing or rewriting some > text (including internal Javadoc documentation), but not development of any > logic, code experiments, benchmarking, etc. > > The question is arisen here: > https://github.com/apache/incubator-druid/pull/6370#discussion_r219694721 >
