Tracking issue for tool dev SIG on January 22nd

[bernt-matthias]

We decided to have a small hackaton on the 22nd of January. Idea:

• Everyone of picks at least 1 issue or PR and prepares it for discussion (in the SIG meeting)
  • Check for new features in the release notes of the upstream project
  • Check why the tests are failing
  • Check if any corresponding issue for the tool has been reported.
  • If possible already fix the problems and make the PR ready
  • Check if .lint_skip file exists and remove. Review the tool for possible improvements.

Can also be items from other tool repos

In order to avoid duplicated work list PR and issues you want to look have below and if possible add cofest label (if you can add labels).