Fabrice Bellingard | SonarSource |
--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/ba187d6b-4808-4162-8825-f60d3b6e2340%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Simon Brandhof | SonarSource
Co-Founder & Tech Lead
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/52117f4c-9a4b-4c20-9492-f905f55fd538%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi,
Thanks for providing the first RC of SQ 6.5. Had a first short look to it on https://next.sonarqube.com/sonarqube/about.
Some first comments:
Regards,
- · in general: prefer heatmaps against this bubble charts
- · measures:
- · some subpages have treemaps (e.g. All Measures / Coverage Measures) some not
- · Would anyway call it heatmaps?
- · Activity
- · Activity / Overview: should be technical debt?
- · Activity / Custom: hard to read because all characteristic curves are somehow blue
Hi Ann,
Feedback is a gift – just accept it. And I think you also have to see it positive: as long you get feedback there is still interest in your product.
The thing I’m disappointed is that starting with SQ 5.6 every new version focuses mainly on internal clean-up and removing features. From new versions I would normally expect more customer value and not less. And looking to the forums it seems that I’m not the only one with this opinion.
… or technical debt in $ (wha? this ship sailed a long, long time ago).
SQ was starting with the proposal to be a tool to measure Technical Debt. I like to quote Dave Smith: “Technical Debt is a wonderful metaphor developed by Ward Cunningham to help us think about this problem. In this metaphor, doing things the quick and dirty way sets us up with a technical debt, which is similar to a financial debt.” The problem is that the executives understands only $. So removing the total cost and replace it with home-made metrics (like A-E …) removes a lot of benefit (at least for the executives).
… and yes I remember the good old times where you had an overview picture with total technical debt in $ and a percentage distribution into different areas like issues, coverage, duplicates, … .
… in general: prefer heatmaps against this bubble charts
For me heatmaps are much easier to read. It gives a better overview of all components/files, their size and their current state. With bubble charts I typically have the problem of overlapping circles.
… As an example, if we tried to draw a treemap for the number of Code Smells I guess it's easy to say that 0 issues would be green, but how many code smells should it take to get to red? Whatever the number, if you add one more, then the scale shifts, and what was yellow yesterday becomes green(ish) today.
Understand this. But why not using the quality gate settings in such cases? Green= quality gate criteria fulfilled; red=failed. If no quality gate condition or report exist make it grey. This would also be beneficial for metrics like size where you at least get an overview about folder/files and their size.
Would anyway call it heatmaps?
All Measures / Coverage Measures: https://next.sonarqube.com/sonarqube/component_measures/metric/coverage/list?id=org.sonarsource.java%3Ajava
For me the word heatmap would be more descriptive than treemap.
In fact, the scale here is not coder-hours but plain issue count. "Overview" may not be the best name, but Technical Debt surely doesn't fit. It's possible that this chart will evolve, but nothing has been finalized.
For my understanding SQ should still be a tool to measure Technical Debt? So a chart to visualize the overall technical debt would be helpful.
Looking forward to the next LTS,
Günter
Built-in quality profiles ... profiles provided by plugins are now read-only and automatically updated on plugin upgrade
--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/df018317-fc91-422c-9cbe-720192181cf7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Note that before 6.5 the new versions of your built-in profile were not applied to existing profiles. For example a new rule had to be manually activated, even if present in the plugin.
... then a user profile should inherit the built-in profile (see operation "Change Parent"). Changes on each new upgrade will be propagated.
Regards,