I’m using SonarQube 7.9.1 Community Edition and recently requested an improvement to how the New Code/leak Period can be specified.
After doing some more research, I discovered that the leak period concept is in the process of being merged/refactored in such a way that would, if I understand correctly, eliminate the possibility of setting a version or a date as the New Code Period:
On my team, these are essentially the only kinds of value we use for our leak period. Specifying a version (which should probably just be called a “label”), for example, allows us to easily compare against a “moving target” that gets scanned regularly even if it always has the same version label. It’s perhaps especially important to keep version and date options for users of CE, which doesn’t offer branch support.
Can someone on the SonarSource team close to this feature update please clarify the expected new behavior, motivations behind the change, implications for CE, whether or not my class of use cases are considered as valid or irrelevant, and offer any workarounds or plans for addressing these concerns before 8.0 is released?