Defining a Legacy Date
You play Quboo to fix only old issues. The reason is simple: it will be easy to cheat otherwise. You can fix your own ugly code one hour after you introduced them. Not nice.
Defining what you consider Old Code (or Legacy Code) can be simple: just take six months back. Or you can base that date on something more meaningful for your organization: a previous release, for example. You could also set it to the first day on which you deploy the game.
The Legacy Date in Quboo can be set in two modes: fixed date and sliding.
- If you choose a fixed date, the legacy date will not move with your campaigns. This is perfect if you want to focus on fixing a particular piece of your codebase and you know it’ll take time to complete.
- If you choose the sliding method, the legacy date will be set to an offset relative to the start date of your campaign. You can use this method if you allow the introduction of some code quality issues here and there but you want to get them cleaned eventually.
What about creating technical debt?
While you fix old code-smells do not forget to avoid including new ones. Otherwise, you will never pay your technical debt.
A good way to keep an eye on the new code is by setting a Quality Gate in SonarQube. You can start by setting the gate to your current status so you don’t allow the issues to go up. Then, remember to tune it every now and then to lower the threshold as you keep improving your code quality with Quboo.