2 ms·
You are describing policy issues with a technical solution. The solution to policy issues such as those is to make it policy to only use the solution at approp
by kbenson 10y ago
You are describing policy issues with a technical solution. The solution to policy issues such as those is to make it policy to only use the solution at appropriate times.
If you only allows TODO after a discussion (e.g. TODO: We decided to forego implementing X at this time, but we may need it later, as per project lead Y).
It does not prevent prioritization or ownership, and there's nothing to prevent a corresponding entry in some management system (and indeed, you can put the ID from that system in the TODO).
That said, often there's things you want to signpost specifically for future developers (including yourself) which may not rise to the level of needing a ticket assigned or external tracking (or that may be complicated due to bureaucracy or or you measure goals being met). There are plenty of reasons to have an additional channel to signal information directly to a dev. Just don't make that instead off the official channels of communication without good cause.