3 ms·
I think it's most important that every line changed in production code can be backtracked to a ticket in the "feature management database" whether it's Jira or
by fsloth 7y ago
I think it's most important that every line changed in production code can be backtracked to a ticket in the "feature management database" whether it's Jira or whatever. This simple rule helps immensely in keeping codebases in good shape.
This is the only clearcut rule that I can think of that is obvious and non-negotiable.
Other things of course make sense (document something in code, other things somewhere else) but are more matters of taste and culture.
- oneplane 7y agoWe split it out: non-ticketed changes are recorded by forcing commits with specific commit formatting that puts out a changelog at intervals. That gets you a log of changes that can be either tracked back to a ticket or are self-describing. (public examples are the Angular Commit Message Conventions or the way saltstack uses that stuff https://github.com/saltstack-formulas/.github/blob/master/CONTRIBUTING.rst https://github.com/saltstack-formulas/.github/blob/master/CO... - you basically enforce some rules using commitlint and record logs using semver, even if you end up not using the versioning for your software)