After working on https://github.com/devfile/api/issues/1326 it was discovered that the current release process for the devfile registry operator is presenting issues when trying to automate the tasks required to cut a release. Currently we are using release branches that represent a major version, such as release-v0, release-v1. This presents issues when we are trying to cut a new minor or patch release to the respective major where the base is coming from main. The automation runs into issues because of differing git histories between the release branch and main, resulting in manual merge resolution which defeats the purpose of automating the process. In order to prevent this from happening we need to adjust the release process to better fit our needs.
Which area/kind this issue is related to?
/area registry
Issue Description
After working on https://github.com/devfile/api/issues/1326 it was discovered that the current release process for the devfile registry operator is presenting issues when trying to automate the tasks required to cut a release. Currently we are using release branches that represent a major version, such as
release-v0,release-v1. This presents issues when we are trying to cut a new minor or patch release to the respective major where the base is coming frommain. The automation runs into issues because of differing git histories between the release branch andmain, resulting in manual merge resolution which defeats the purpose of automating the process. In order to prevent this from happening we need to adjust the release process to better fit our needs.Acceptance Criteria