Differences between revisions 21 and 23 (spanning 2 versions)
Revision 21 as of 2019-08-12 23:12:23
Size: 2690
Comment: remove "Plinth"
Revision 23 as of 2019-09-15 13:45:36
Size: 3356
Comment: add steps for backports
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
    * Remove any {{{(Closes: nnnn)}}} that refer to Salsa issues rather than Debian bugs.
Line 39: Line 40:
== Backports ==

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

 1. Check out the debian/buster-backports branch.
 1. 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.
 1. Run {{{dch --bpo}}} to add the debian/changelog entry for the new backport release.
 1. Commit this change with message "Release <version> to buster-backports".
 1. Build the binary package with {{{gbp buildpackage -v<previous version>}}}.

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 plinth functional tests against current master.

  3. Check if boot process happens on one image.

Release

Releases are currently done every 2 weeks.

  1. First, check if there are any uncommitted changes on weblate. Commit if there are any.

  2. Update translation strings by running python3 setup.py update_translations. Commit.

  3. 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.

  4. Update the Release Notes on the wiki. This is a summary of changes that are relevant to end users.

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

  6. Update the version number in plinth/__init__.py.

  7. Run dch -r and finalize the changelog.

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

  9. 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

  10. Build the source-only package using gbp buildpackage --changes-option=-S.

  11. Sign the dsc and changes files with debsign.
  12. Upload the changes file with dput.
  13. When the release is accepted into Unstable, you will get an email "Accepted plinth x.y.z (source) into unstable".
  14. 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)

  1. Publish changelog on various channels - discussion forum mailing lists, irc and matrix groups, Twitter or GNU Social etc.

  2. Upload new image to Vagrant Cloud.

Backports

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 gbp buildpackage -v<previous version>.


CategoryFreedomBox