Skip to content

Adapt CI jobs involved in producing release tarballs to work with Automake & Sphinx

  • Source tarballs for master should be produced using make dist.

  • Release tarballs for master and v9_16 must contain Sphinx-generated documentation files.

Internal discussion led to the following solution:

  • Include the ARM in HTML, PDF, and EPUB formats in the release tarball (i.e. in the FTP directory for a given release).

  • Do not prepare any separate documents with just the release notes, but point the reader towards them.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information