Criterion v2.4.0 release

[Snaipe]

I think the recent fixes addressed most of the showstopping issues for v2.4.0; @MrAnno how do you feel about the current state of bleeding for a new release?

Concurrently, I'll go through every open issue to see whether this will be fixed by the release, and if not whether this is a showstopper for the new version.

Prerequisites:

• Check that the readthedocs build+publish still works, maybe use a test tag

Release checklist:

• Update the ChangeLog
• Merge bleeding into master (with a merge commit)
• Make an annotated tag (with the changelog as message)
• Tag BoxFort v0.1.2 at the commit that the Criterion release uses (currently 46cfaeb)
• Send a new version notification to the mailing list
• Party! 🎉

[Snaipe]

Something I haven't checked in a while is whether the readthedocs generator still works; we'll probably need to make a test tag and test it out first, because re-publishing docs for a tag was pretty much impossible last time I checked.

[MrAnno]

Sounds good to me :)

I'm not sure about backward compatibility with v2.3.3, I'll do some tests on the current release candidate (syslog-ng has 182 exotic Criterion tests, I am going to give it a go.).

[MrAnno]

In the meantime:

ABI compatibility info, click to expand!

[Snaipe]

These removed symbols should never have been exposed to begin with; looks like I'll have to audit symbol visibility on the new version

[MrAnno]

Can I help with collecting entries for the changelog?

[Snaipe]

Sure; I usually go through the git log of everything that happened between the release candidate and the last release, then categorize & format them accordingly.

[MrAnno]

Thank you, I'll do the same.

I've tested the release candidate with the mentioned syslog-ng tests. Most of them work properly with the below warnings, which is absolutely fine:

boxfort-worker: Symbol `criterion_options' has different size in shared object, consider re-linking

I have 2 crashes, which I'm currently investigating. Hopefully they are unrelated to Criterion.

[kugel-]

Thanks for working on 2.4.0. If time permits (and I don't forget) I'll check our inhouse tests work fine with the new release.

[MrAnno]

Everything seems to be fine from my side. A ton of warnings have appeared, #403 fixes them.

[Snaipe]

@kugel- I usually go through a round of release candidates first, so we'll have plenty of time to let users check their tests against the new release once we start the release process.