3402
Comment: clarify previous version
|
3644
add reference to freedombox-buster-dev vagrant box
|
Deletions are marked like this. | Additions are marked like this. |
Line 50: | Line 50: |
1. There is a [[https://app.vagrantup.com/freedombox/boxes/freedombox-buster-dev|vagrant box]] based on buster that can be used for testing. Set it up using [[https://salsa.debian.org/freedombox-team/plinth/snippets/273|this Vagrantfile]]. |
This is a brief description of the process of releasing a new version of FreedomBox.
Pre release (work in progress)
Check that unit tests are not broken.
Run plinth functional tests against current master.
- Check if boot process happens on one image.
Release
Releases are currently done every 2 weeks.
First, check if there are any uncommitted changes on weblate. Commit if there are any.
Update translation strings by running python3 setup.py update_translations. Commit.
- Update debian/changelog in the Plinth repository, including details that are relevant to contributors.
You can run gbp dch -a --multimaint-merge, then remove duplicates.
Also 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.
Update the Release Notes on the wiki. This is a summary of changes that are relevant to end users.
Fetch the latest manual by running make -C doc fetch. Commit.
Update the version number in plinth/__init__.py.
Run dch -r and finalize the changelog.
Commit these changes with the message "Release <version> to unstable".
Build the package using gbp buildpackage.
- Check for any new lintian errors.
- Recommended to test by installing the package in a development environment, or by building a freedom-maker image with --custom-package.
- You can also run autopkgtest:
autopkgtest --apt-upgrade -B <new freedombox .deb> <source folder> -- lxc --sudo autopkgtest-unstable-amd64
Build the source-only package using gbp buildpackage --changes-option=-S.
- Sign the dsc and changes files with debsign.
- Upload the changes file with dput.
- When the release is accepted into Unstable, you will get an email "Accepted plinth x.y.z (source) into unstable".
- After the release is accepted into Unstable, create a 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)
Publish changelog on various channels - discussion forum mailing lists, irc and matrix groups, Twitter or GNU Social etc.
- Upload new image to Vagrant Cloud.
Backports
A release can be backported to stable-backports after it has migrated to testing.
- Check out the debian/buster-backports branch.
- 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.
Run dch --bpo to add the debian/changelog entry for the new backport release.
Commit this change with message "Release <version> to buster-backports".
Build the binary package with gbp buildpackage -v<previous> where <previous> is the previous version in backports.
There is a vagrant box based on buster that can be used for testing. Set it up using this Vagrantfile.