GBL respin process

This page describes the Generic Bootloader (GBL) respin process to submit a request for a new release of GBL.

A respin is a new release of GBL. To submit a respin request, follow these steps:

  1. Fill out the GBL respin request form and reach out to your Google point of contact immediately.

    • This form creates a GBL respin request bug. Note the bug ID.

  2. Prepare your patch:

    • Verify that the patch is merged into the GBL development branch.
    • Apply the patch to the appropriate GBL release branch.
    • Amend the cherry-picked patch to include the bug ID created in step 1 as a Bug: XYZ tag in the commit message.

    Example: To cherry-pick a change list (CL) from <development-branch> to <release-branch>:

    # 1. Check out the target release branch
git checkout <release-branch>

# 2. Fetch the upstream development branch (Source of Truth)
git fetch aosp <development-branch>

# 3. Cherry-pick the commit (Preserving metadata)
git cherry-pick -x <commit_hash>

# 4. Update the commit message to include the Respin Bug ID
# (Don't remove existing Bug IDs or change the Change-Id)

  3. Submit the bug. The following occurs after you submit the request:

    • Review process:

      • The Google GBL team reviews the request and approves it or assigns it back to you if the team needs more information.
      • After agreeing on a fix, the GBL team reviews the change.
      • The GBL team merges, builds, tests for regression, and certifies the change.

    • Release: