Please apply the following checklist before releasing.
- Sources
- - The version number is correctly marked in CMakeList.txt, in macros
+ - The external patches (Debian, etc) are integrated.
+ The COPYING file is aligned with Debian's copyright file.
+ - The version number is correctly marked in CMakeLists.txt, in macros
SIMGRID_VERSION_MAJOR and friends.
- The "make distcheck" target works (testing that every files needed
to build and install are included in the archive)
- ChangeLog file
- All changes are documented
- The release date is indicated below the changes
- - The release is marked as stable above the changes
+ - The release is marked as stable above the changes (remove the UNRELEASED marker)
- The release dub name matches the one given in NEWS file
- NEWS
- The most notable changes of the version are documented
included through globbing. The best is to use a clean checkout:
\verbatim
cd /tmp
-git clone ~/Code/simgrid
+git clone --depth=1 ~/Code/simgrid
cd simgrid
cmake . && make dist
\endverbatim
- Push the archive files (tar.gz and jar) on gforge
- Post a news on gforge (before updating the website)
- Update the link scm.gforge.inria.fr:/home/groups/simgrid/htdocs/simgrid/latest
+ (and create the directory of the next version)
- Rebuild and resynchronize the website so that the file gets visible
from our download page.\n
- Edit org/org-templates/level-0.org to change the release version, the tgz link and the jar link.
- emacs org/site/download.org and C-c C-c the first source block to refresh the download.
- emacs org/site/documentation.org and edit the version links.
- make -C org all sync
- - git commit && git push
+ - git commit -a && git push
- Announce the release
+ - Document the tag on https://github.com/simgrid/simgrid/releases
- Mail the simgrid-user mailing list
- the NEWS chunk in the mail;
- the ChangeLog chunk as attachment