- The release dub name matches the one given in NEWS file
- NEWS
- The most notable changes of the version are documented
- The release dub name matches the one given in NEWS file
- NEWS
- The most notable changes of the version are documented
- The date of the release is marked in the title
- Tests
- The "make distcheck" target works (tested by jenkins)
- The date of the release is marked in the title
- Tests
- The "make distcheck" target works (tested by jenkins)
- Tutorials and derivative projects build correctly
https://framagit.org/simgrid/simgrid-template-s4u/pipelines
https://framagit.org/simgrid/external-projects-ci/pipelines
- The python module builds (see below).
- Tutorials and derivative projects build correctly
https://framagit.org/simgrid/simgrid-template-s4u/pipelines
https://framagit.org/simgrid/external-projects-ci/pipelines
- The python module builds (see below).
- CMakeLists.txt (in macros SIMGRID_VERSION_*)
- sonar-project.properties
- docs/source/conf.py
- setup.py
- Commit and push to both framagit and github
- CMakeLists.txt (in macros SIMGRID_VERSION_*)
- sonar-project.properties
- docs/source/conf.py
- setup.py
- Commit and push to both framagit and github
- If it's not successful, fix it and push again
- Once it's successful everywhere: merge 'master' into 'stable' and push it to framagit
- You can interrupt the build on jenkins, as it was tested just before
- If it's not successful, fix it and push again
- Once it's successful everywhere: merge 'master' into 'stable' and push it to framagit
- You can interrupt the build on jenkins, as it was tested just before
- Download the simgrid-doc-3.X.Y (artefact of pipeline 'pages' on framagit)
Download the tgz file (artefact of the pipeline 'stable' on framagit)
- Download the simgrid-doc-3.X.Y (artefact of pipeline 'pages' on framagit)
Download the tgz file (artefact of the pipeline 'stable' on framagit)
- Tag the git repository v3.XX.X and push it to framagit and ghub
- Document the tag on framagit and ghub
- Tag the git repository v3.XX.X and push it to framagit and ghub
- Document the tag on framagit and ghub
- Add a link to the version of the ChangeLog that comes with this tag.
https://framagit.org/simgrid/simgrid/-/blob/v3.29/ChangeLog
- Update the website
- Add a link to the version of the ChangeLog that comes with this tag.
https://framagit.org/simgrid/simgrid/-/blob/v3.29/ChangeLog
- Update the website
- jed .gitlab-ci.yml
- Change the link to the simgrid-doc-3_XX.zip file
- Only keep 2 old versions so that people don't find older ones in google
- jed .gitlab-ci.yml
- Change the link to the simgrid-doc-3_XX.zip file
- Only keep 2 old versions so that people don't find older ones in google
- 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
- 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
- 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
- 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.
- 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.
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)
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)
- 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)
- 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)
- 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
- 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