+ - Hall of Fame in the mail
+ git shortlog -se v3.29..
+ - Link to the ChangeLog on framagit (the version of that tag)
+ - Also mail some other lists (G5K users)
+- Release the debian package
+ - rm -f ../simgrid_3.*+dfsg.orig.tar.xz
+ - uscan # download the new version
+ - gbp import-orig ../simgrid_3.*+dfsg.orig.tar.xz
+ - dch -i "New upstream release" # + copy the NEWS into debian/changelog
+ - git mv debian/libsimgrid3.XX.install debian/libsimgrid3.XY.install
+ - edit debian/control: s/simgrid3.XX/simgrid3.XY/
+- Update the simgrid/package.py for spack: https://gitlab.inria.fr/solverstack/spack-repo
+- Push the stable branch to github to rebuild and push the stable Docker images
+ - It downloads the latest tag on framagit
+ - If it was done automatically at some point, make sure that it's really the latest stable,
+ as things get sometimes out of synch to the point that the github action re-build the previous release.
+ If this happens, just rerun the docker-stable action. Nothing should have been broken.
+ - Doing the same manually: cd tools/docker && make stable && make tuto-s4u tuto-smpi
+ (tuto-mc is not based on simgrid/stable but rebuilds from the git)
+ - Once the new images are built, trigger a rebuild of the simgrid-template-{s4u,smpi} repositories on framagit
+- Add the new simgrid/stable image to the .gitlab-ci.yml of:
+ - https://framagit.org/simgrid/simgrid-template-s4u/
+ - https://framagit.org/simgrid/simgrid-template-smpi/
+
+@subsection inside_release_c_postrelease Post-release cleanups
+
+- Create the template for the next release in ChangeLog and NEWS files
+ Release Target date: https://en.wikipedia.org/wiki/Equinox
+- Bump release number to 3.X.1 in CMakeLists.txt sonar-project.properties docs/source/conf.py setup.py
+- Deal with deprecations:
+ - jed include/xbt/base.h: Introduce the next XBT_ATTRIB_DEPRECATED_v??? macro
+ - Kill the one for the current release and remove all code that were
+ mandated by the deprecated functions (both in source and headers).
+ - Do the possible cleanups now that these features are gone.
+- Regenerate the unstable docker with this new version
+
+Release numbering semantic:
+ - 3.X is a named release.
+ - We have 4 named releases per year (for each equinox and solstice)
+ - The ChangeLog and NEWS are complete and informative
+ - All tests pass on all ci systems (or the workarounds are documented)
+ - We provide and store a source .tar.gz on framagit
+ - Deprecated symbols remain usable for at least 3 named releases (~1 year)
+ - These releases are announced to the users
+ - 3.X.Y where Y is even: dot release of 3.X, prerelease of 3.(X+1)
+ - We provide and store a source .tar.gz on framagit
+ - These releases are NOT announced publicly, nor really documented.
+ The idea is to have something close to a rolling release.
+ - External projects can depend on dot releases to loosen their
+ release process from ours, when 4 release a year is not enough
+ - 3.X.Y where Y is odd: git current status between two releases
+ - No expectations on such versions
+ - Example
+ - 3.22.4: unannounced/loosely documented stable release
+ - 3.22.5: git status somewhere between the release of 3.22.4 and the next one
+ - 3.23: Documented and announced stable release
+