This is a brief description of the process of releasing a new version of FreedomBox.

Pre release (work in progress)

  1. Check that unit tests are not broken.

  2. Run freedombox functional tests against current master.

  3. Check if boot process happens on one image.


Releases are currently done every 2 weeks.

  1. Check if there are any uncommitted changes on weblate. Commit if there are any.

  2. Clone the freedombox repository, and check out latest master branch.
  3. Update translation strings by running python3 update_translations. Commit.

  4. Run gbp dch to update debian/changelog.

    • Check plinth bugs to see if any Debian bugs should be closed by the changes in the release.

    • Remove any (Closes: nnnn) that refer to Salsa issues rather than Debian bugs.

  5. Update the Release Notes on the wiki. This is a summary of changes that are relevant to end users or otherwise important to note.

  6. Fetch the latest manual by running make -C doc fetch. Commit.

  7. Update the version number in plinth/

  8. Run dch -r and finalize the changelog.

  9. Commit these changes with the message "Release v<version> to unstable".

  10. Build the package using gbp buildpackage.

    • Check for any new lintian errors.
  11. Run autopkgtest:
    • autopkgtest --apt-upgrade -B <new freedombox .deb> <source folder> -- qemu ~/autopkgtest/sid

  12. Test the new package by installing the package in a development environment, or by building a freedom-maker image with --custom-package.
  13. Build the source-only package using gbp buildpackage --changes-option=-S.

  14. Sign the dsc and changes files with debsign.
  15. Upload the changes file with dput.
  16. When the release is accepted into Unstable, you will get an email "Accepted plinth x.y.z (source) into unstable".
  17. After the release is accepted into Unstable, create a (signed) tag for the release. Push commits and the new tag to the Salsa repository.
    • Weblate will automatically update with the latest changes.

Post release (work in progress)

  1. Publish changes from Release Notes on various channels:
  2. Upload new image to Vagrant Cloud.


A release can be backported to stable-backports after it has migrated to testing.

  1. Check out the debian/buster-backports branch.
  2. Merge the latest release tag.
    • There will be a merge conflict due to debian/changelog. Resolve it by arranging the releases in the correct chronological order.
  3. Run dch --bpo to add the debian/changelog entry for the new backport release.

  4. Commit this change with message "Release <version> to buster-backports".

  5. Build the binary package with DIST=buster-backports gbp buildpackage -v<previous> where <previous> is the previous version in backports.

  6. There is a vagrant box based on buster that can be used for testing.

  7. Run autopkgtest:
    • autopkgtest --apt-upgrade -B <new freedombox .deb> <source folder> -- qemu ~/autopkgtest/buster

  8. Sign the dsc and changes files with debsign.
  9. Upload the changes file with dput.
  10. After the release is accepted into backports, create a (signed) tag for the release. Push debian/buster-backports and the new tag to the Salsa repository.