Releasing Savane

Releases for the Translation Project

We do release tarballs in the download area of the administration group. These releases serve as references for the Translation Project where our UI is localized. Nonetheless, we do make efforts to ensure that the tarballs look like real releases and e.g. can successfully pass distcheck.

In the same area, we may also release auxiliary files like dumps of sample Savane database.

Working branches

Our Savane repository has three permanent branches:

master: The "stable" branch: it doesn't accept non-fast-forward commits, it is used as the base for all other branches.
i18n: The branch where the development is done. The commits are amended in this branch until they are absorbed in the master branch.
frontend: The branch the frontend runs.

Corresponding source code for specific machines

The requirement of the AGPL to offer the corresponding source code is triggered in these cases:

The PHP code of Savannah Web UI. When Savane is built, a distribution tarball is generated and installed next to PHP files. Normally, Savane serves that file as the "Corresponding source code" link at the bottom of the page; as a fallback for the non-realistic case when the tarball is absent, a link to the respective commit at our Cgit instance is provided. Keeping the frontend branch at the specific commit makes sure that it is accessible and git gc doesn't remove it.
The sv_membersh script for SSH access, as of 2024-04 used at the download server. The source code of Savane is provided from the same machine through RSYNC, which is one of the protocols offered for downloading the hosted data.

Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. This file is offered as-is, without any warranty.