Skip to content

Release Checklist

Vasundhara Shukla edited this page Nov 29, 2022 · 3 revisions
  • Check the open issues which can be fixed and accommodated in the release.
  • Validate if any resource behaviour/api spec has changed from the previous release and incorporate the changes in the provider.
  • Check for any upgrade scenarios and test them with the respective and dependent resources.
  • Build the provider and test for all new resources added and test again by clubbing with previously present resources.
  • Run make test (tests linters, go fmt, go vet).
  • Run all unit tests.
  • Run acceptance tests.
  • Get engineering manager's nod and product manager's approval before a new release.
Clone this wiki locally