Update latest version to v4.1.0
ok so far ... but shouldn't 4.1.0 be tagged (and not touched any more) with these dates, and then changing the version number in master to 4.2.0 (#4659)? Sorry now I've seen; The tag has coerrect dates.
We definitely need some automatism for these things!
If @casella overrides me, the master version shall be named 4.1.0. But: I'll never accept this PR without an empty release notes table!!! If the name "4.2.0 dev" is acceptec within MAP-Lib, we could use #4659
#4659 will be used instead. There is agreement that the development branch is named 4.2.0. And: There is the table missing for the release notes -> closed without merging.