Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft for 1.2.2 release #1683

Closed
guwirth opened this issue Feb 8, 2019 · 4 comments
Closed

Draft for 1.2.2 release #1683

guwirth opened this issue Feb 8, 2019 · 4 comments
Assignees
Labels
Milestone

Comments

@guwirth
Copy link
Collaborator

guwirth commented Feb 8, 2019

Please review:

We are pleased to announce the SonarQube C++ Community Plugin version 1.2.2.
See lists below for features added and bugs fixed in this release.

SonarQube compability

Enhancements

Bugfixes

Known Issues

For an up to date list of known issues see the issue tracker.

  • not compatible with Java 9
  • Ensure that a rule is enabled if you get no results. In new SQ versions the default profile is read-only. The cxx plugin does not enable all rules per default.
  • Starting with SQ 6.2 there are some new metrics and some are no more available. Please have a look to the SonarQube release notes.
  • duplicated_lines_density values are different with SQ 7.5
  • test execution metrics are not supported
  • The Cppcheck plugin is deprecated and not working in parallel to this plugin. This plugin provides an own Cppcheck sensor.
  • C plugin and JSON Compilation Database support are experimental only

Thanks ....

go to all contributors (in alphabetical order):

@guwirth
@ivangalkin

... and all people which were active on the issue tracker!

@guwirth guwirth added this to the 1.2.2 milestone Feb 8, 2019
@guwirth guwirth self-assigned this Feb 8, 2019
@ivangalkin
Copy link
Contributor

👍 thank you!

@guwirth
Copy link
Collaborator Author

guwirth commented Feb 9, 2019

I will release 1.2.2 today.

Seems that next SQ 7.7 version will also be next LTS? For our next version I see the main focus in removing deprecated API and updating the wiki.

Some other points I have in mind:

  • Do we need the c plug-in? Or can we remove it?
  • Someone using our lint tool (part of cxx plug-in)? Or can we remove it?
  • Who is using XPath?
  • Who is using custom checks?
  • I would like to remove checks marked deprecated

Any other ideas/comments?
I would tend to set the next version number to 1.3?

@ivangalkin
Copy link
Contributor

ivangalkin commented Feb 9, 2019 via email

@guwirth
Copy link
Collaborator Author

guwirth commented Feb 9, 2019

Hi @ivangalkin,

Yes makes sense. I will wait for it. One other comment to Cppcheck. There are some Vulnerability. Think following the SQ definition a tool like Cppcheck don’t create Vulnerability? Maybe you can set it to Bug or Code Smell?

Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants