saros
saros copied to clipboard
Add todo policy to documentation
trafficstars
Add the following policy to the documentation:
Always open a new issue if you added a TODO comment in your code
I think it is more relevant to define a best-practice to write a TODO: A TODO should contain the information:
- What should be adjusted and (which is often missing) why. Without the "why", other develops are not able to evaluate whether the TODO is still relevant.