upgrade to checkstyle 8.28

[romani]

https://checkstyle.org/releasenotes.html#Release_8.28 , upgrade version at https://github.com/checkstyle/sonar-checkstyle/edit/master/pom.xml#L88

[romani]

@muhlba91 , it might be reasonable to release update to 8.29 before we migrate Sonar 7.9 (#232), as it looks like we stuck on integration testing.

[romani]

@muhlba91, please try to do release yourself

[romani]

@muhlba91 , please cut a release.
All other possible improvements can go to next release,
core library will have next release at this Sunday(26th Jan 2020).

It would be awesome to update (to new version of sonar):
https://github.com/checkstyle/sonar-checkstyle/wiki/How-to-build-test-plugin-on-local
https://github.com/checkstyle/sonar-checkstyle/wiki/How-to-make-release

[muhlba91]

PR: SonarSource/sonar-update-center-properties#87
SS: https://community.sonarsource.com/t/new-release-sonar-checkstyle-4-28/19166

@romani please do step 6:

1. email announcement in google group: either it doesn't exist anymore or i don't have any permission to see the group
2. sourceforge news: i don't have permissions
3. twitter: same, no permissions
   <- btw, are they all really needed or can we start limiting them and grant permissions accordingly?

[romani]

@muhlba91 , thanks a lot for release.

I removed from release notes:

replace cobertura with jacoco
infra: add ITs placeholder
infra: use maven-enforcer-plugin for jdk and maven check
infra: update findbugs to spotbugs
infra: put sonar-application-7.9.2.zip to maven cache

I try to not bother users with inner updates, and keep them be aware of main changes. We propably need to add "infra:" to shell script that filter notes.

are they all really needed or can we start limiting them and grant permissions accordingly?

they are not really needed, it was just habit.
It is good to do, but ok to skip.

[romani]

twitter

you can twit it from your account and I will retwitt.

sourceforge

we deprecate sourceforge usage ... I can copy twit content to RSS at sourceforge. I am not sure about sourceforge future, I can not measure how much people read this content.

mail-list

https://groups.google.com/forum/#!members/checkstyle-announce
We have only 21 members in this mail group .... something told me to deprecate this new channel.
We do have almost strict time based release cycle ... so might looks for github notifications about releases only.

[romani]

@muhlba91 , please share with me your sourceforge account, I will try to grant you permission for posts.
can I use your gmail account to grant you permission for checkstyle-announce channel ?

Twitter account is access it not shareable, or I do not know something ....

[muhlba91]

@romani yes, my google account is good :)
my sourceforge account is the same as my github one: muhlba91

yes, i believe it would be nice to deprecate (nearly) unused channels - it adds overhead just for the benefit (if they do care) for a few people.
maybe it's better to facilitate all communication to one channel to have an overview of everything and everyone will know where to find which information easily?

[romani]

I added you as developer sourceforge, please check if can make post at https://sourceforge.net/p/checkstyle/news/
I invited you to mail list, ones you confirm membership, I can see how to grant you permissions.

maybe it's better to facilitate all communication to one channel to have an overview of everything and everyone will know where to find which information easily?

I more and more inclined to use Github as notification system only ("Releases only").

Twitter is just for fun, I keep twitter as thread of my findings about static analysis and related articles.

RSS - it is impossible to get to know size of audience.
mail-list - probably can be deprecated, it is just a habit from the past that I created when migrated project out of sourceforge a long time ago.