- Create X.Y branch if first bugfix release

  git branch X.Y X.Y.0
  git checkout X.Y

- See if makes sense to cherry-pick other fixes/changes

- Update NEWS if anything major, commit

- Update version in manifest, cli.sh, commit and push:

  git ci -a -m "Bump version to X.Y.N"
  git push

- Regenerate odb.sh, cli.sh

- If need to rebuild build2-toolchain:

  - Create branch as above, then:

    git submodule update --checkout

  - Add the branch value for each entry in .gitmodules:

    branch = X.Y

  - Then checkout and commit updated submodules:

    git submodule update --remote <submodule>

  - Update version in manifest as above

  - Regenerate odb.sh (may need to checkout old version or copy old),
    cli.sh as above.

  - Stage and diff with previous version for sanity check.

- Dist to queue:

  etc/stage-pkg -q -d -c <group> <proj>

  If need to dist build2-toolchain, then rename X.Y.N-1 to X.Y.N in
  private/baseutils, then:

  etc/stage -b -p

  Verify build2-toolchain works by building locally.

- @@ TODO: Test queue.

- Move package from queue to the appropriate repository, normally
  replacing the old package.

- Regenerate the repository and publish (remove -p if also publishing
  build2-toolchain):

    cd cppget.org
    git -C repository add .
    git -C repository status
    ./update

    cd ..
    etc/publish -p

- Update download links/checksums if changed build2-toolchain.

- Tag the bugfix release:

  git tag -a X.Y.Z -m "Tag version X.Y.Z"

  Also in build2-toolchain if applicable.

- Commit cppget.org/repository/ (see history for procedure)

- Commit private if changed build2-toolchain.

- Write and send announcements, remember to include checksum.

- Switch back to master and regenerate cli.sh/odb.sh