IKOS 3.2 -- Release planning

[ivanperez-keera]

The release of IKOS 3.2 has been approved.

I propose we publish a release candidate. It's a bit of an extra step, but it may help us catch installation issues.

A way to do this would be to bump the version number to 3.2-rc1 and just merge it to master. We can also tag it, although I'd remove that tag once we have a final release, and we can make it clear in the discussions that this is a release candidate.

After that, and if no issues are reported, we bump that to 3.2, tag and release.

The CI job passes fine with "3.2-rc1" as PACKAGE_VERSION in the CMakeLists.txt file. See the actions "Confirm that it runs", which print the correct version number:

• Linux: https://github.com/ivanperez-keera/ikos/actions/runs/7222243755/job/19678854834
• Mac: https://github.com/ivanperez-keera/ikos/actions/runs/7222243754/job/19678854827

We'd need to adjust the homebrew formula either way.

I'm open to other ideas about how to best do this. Some people manage releases / release candidates differently.

[ivanperez-keera]

We are proceeding as planned:

• Issue: Release IKOS 3.2-rc1 #251 .
• PR: Update version number to 3.2-rc1 (#251). #252 .
• Tag: https://github.com/NASA-SW-VnV/ikos/releases/tag/v3.2-rc1