From ccf47dd4c352f289a8992eefd25c0bb919657f6a Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Sat, 11 Jul 2020 07:59:28 -0400 Subject: [PATCH] document stable release manifest generation --- static/build.html | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/static/build.html b/static/build.html index 6fb4bd7f..9ccb461d 100644 --- a/static/build.html +++ b/static/build.html @@ -92,6 +92,7 @@
  • Prebuilt apps
  • +
  • Stable release manifest
  • Standalone SDK
  • Android Studio
  • Obtaining upstream manifests
  • @@ -807,6 +808,19 @@ cd src

    A build of Seedvault is bundled as an apk into an external/ repository. There are no modifications made to it.

    +

    + Stable release manifest +

    + +

    Manifests for stable releases are generated with repo manifest -r + after tagging the release across all the repositories in a temporary branch and + syncing to it. This provides a manifest referencing the commits by hashes instead of + just tags to lock in the revisions. This makes verification of the releases simpler, + since only the manifest tag needs to be verified rather than tags for each + repository. This also means the whole release can be verified using the GrapheneOS + signing key despite referencing many upstream repositories that are not forked by the + GrapheneOS project.

    +

    Standalone SDK