Skip to content

Latest commit

 

History

History
40 lines (39 loc) · 2.25 KB

releasing.md

File metadata and controls

40 lines (39 loc) · 2.25 KB
Raw

Releasing

  1. Create releases in repositories with image build jobs with the new release tag:
  2. Verify that the images have been successfully built and pushed with the new release tag:
  3. Some images are not built by us yet. Tag these Docker images manually:
    • nephio/resource-backend-controller
    • nephio/network-config-operator
  4. Update the images in the manifests to point to the new release tag:
  5. Tag any updated packages with a new Porch version number. For example, if you changed the Kptfile in pkg-example-amf-bp to use the new tag for the functions, and the current highest revision number for that package is pkg-example-amf-bp/v3, you need to tag the new one as pkg-example-amf-bp/v4. Note that the sandbox provisioning scripts no longer depend on the Porch revision numbers; instead they use the release tag. However, the user-facing versions in PackageVariant(Set) resources and kpt commands use the Porch revision numbers.
  6. Create releases in the package repositories with the release tag.
  7. Update the sandbox provisioning code:
    • Change the current release tag instances to the new one.
    • Update any e2e tests that use the Porch package version numbers to use the new ones.
  8. Once the PR with the updated sandbox provisioning code passes e2e and is merged, create a release in:
  9. Update the documentation to use the new release tag and the new Porch package version numbers.
  10. Tag the documentation repository with the new release tag.