A release is a bundle with a consistent set of software packages required to use the GENESIS simulator. Internal releases are built on a daily basis, public release are built on a monthly to yearly basis.
A public release has the guarantee that it passes all the regression tests. Internal releases are tested to, but can show minor problems.
The following pre-release procedure would be desirable:
A working buildbot can be a designated tester. Note that it needs to be configured to work on the release branch.
I think the current buildbots don’t do this step.
Every release is identified with a tag. The tag (see below for a definition) allows to reconstruct the release source code from the repositories using the developer package. This helps in solving problems reported by users.
So, for example, for the current release, the tag is des-10, which is the tenth subrelease after starting development of the des milestone.
It might be useful to do “make html-upload” for some packages after the release, to synchronize the content of the website with the content of the downloadable packages.