Prepare changelog for v3.0.0 release

[aphistic]

Update changelog for v3.0.0 release.

[efritz]

There's also a list of releases at the bottom you'll want to make an entry for

[aphistic]

There's also a list of releases at the bottom you'll want to make an entry for

Oh, why do we have that? I would expect people to be able to do that themselves instead of duplicating info. I'm not opposed to it, just curious.

[efritz]

Ah, they link specifically to diffs between versions so people can see the code changes between upgrades.

[aphistic]

Is that something that needs to be explicitly included, or could they rely on the features of GitHub to get that if they want it? The reason I ask is to lower the overhead of doing a release and things to miss.

Edit: Never mind! I didn't realize GitHub does some fancy rendering in the changelog from it.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information