2 \page inside_release Releasing SimGrid
4 \section inside_release_c Releasing the main library
6 \subsection inside_release_c_preconditions Before releasing
8 Please apply the following checklist before releasing.
11 - The version number is correctly marked in CMakeList.txt, in macros
12 SIMGRID_VERSION_MAJOR and friends.
13 - The "make distcheck" target works (testing that every files needed
14 to build and install are included in the archive)
16 - All tests pass on a reasonable amount of platforms (typically,
18 - You also tested to build and install the content of the source
19 archive on a reasonable amount of platforms (typically, 2 or 3).
21 - All changes are documented
22 - The release date is indicated below the changes
23 - The release is marked as stable above the changes
24 - The release dub name matches the one given in NEWS file
26 - The most notable changes of the version are documented
27 - The release date is indicated right below the version name
28 - The release dub name matches the one given in ChangeLog file
30 \subsection inside_release_c_source Building the source archive
32 This should be done from a clean git repository because some files are
33 included through globbing. The best is to use a clean checkout:
36 git clone ~/Code/simgrid
41 If you prefer, you can clean your repository the hard way:
43 git reset --hard master # warning, it will kill your uncommited changes
44 git clean -dfx # warning, it will kill your uncommited changes
48 \subsection inside_release_c_source Building the binary jarfile
50 Get the jarfiles for several OSes on the CI slaves. Use Save under to
51 give a separate name to each of them.
53 - On Jenkins: Mac OSX, Linux 64 and Linux 32 (without boost-context), FreeBSD, NetBSD
54 - On AppVeyor: Windows
56 Once all jarfiles are in a separate directory, run the following to
59 mkdir content ; cd content
61 for j in ../simgrid-linux64.jar ../*.jar ; do unzip -n $j ; done
62 # The content of all jar should be the same, but I prefer using the Linux64 version by default
63 # => unpack it first, and unpack the others with -n (never overwrite)
65 test -e doc/javadoc || echo "YOU ARE MISSING THE DOC"
67 du -sh . # 273M here. Let's strip (Darwin is already good)
68 strip NATIVE/*/*/*.so # Gets BSD and Linux versions, down to 116M
69 x86_64-linux-gnu-strip NATIVE/*/*/lib*dll # Gets Windows, down to 22M
72 zip -r ../simgrid-3_XX.jar * # Produced ../simgrid-3_XX.jar is 7.7M
75 To upload the file on gforge, you need to go to Files/Admin then clic
76 on the Settings icon near to the "Add a version" button, and then on
77 the settings icon of the release you want to change.
79 \subsection inside_release_c_postchecks Check list after releasing
81 - Tag the git repository (don't forget to push the tags to the main repo)
82 - Push the archive files (tar.gz and jar) on gforge
83 - Post a news on gforge (before updating the website)
84 - Update the link scm.gforge.inria.fr:/home/groups/simgrid/htdocs/simgrid/latest
85 - Rebuild and resynchronize the website so that the file gets visible
86 from our download page.\n
87 - Edit org/org-templates/level-0.org to change the release version, the tgz link and the jar link.
88 - emacs org/site/index.org and C-c C-c the first source block to refresh the news.
89 - emacs org/site/download.org and C-c C-c the first source block to refresh the download.
90 - emacs org/site/documentation.org and edit the version links.
91 - make -C org all sync
92 - git commit && git push
93 - Announce the release
94 - Mail the simgrid-user mailing list
95 - the NEWS chunk in the mail;
96 - the ChangeLog chunk as attachment
97 - Also mail some other lists (G5K users), with only the NEWS chunk
98 and the link to the download section
99 - Release the debian package
100 - Create the template for the next release in ChangeLog and NEWS files
101 - Change the release number in CMakeLists.txt