Admin Console : Move code to "main" branch from "dev" during the release cycle

As of now, the releases are configured via pipelines to be done from the "dev" branch. All RC tags are generated in a sequential manner from this branch. This strategy has couple of shortcomings -

• During a release, we have to freeze the branch and further commits have to wait until the release is done
• There is no separate branch that depicts the production deployed code.

The idea is to have the code moved to "main" branch during the release cycle and provide production builds from here. This will seggregate the production and development branches. For this, the pipelines on the main branch need to be configured similar to dev branch, but the package would be deployed to prod marketplace, whereas the dev branch package would be deployed to pre-prod marketplace.

One challenge needs to be discussed - As of now the RC numbers are sequential. Once it is moved to main branch, the last version may not be known.

AC

• Have a main branch with restriction for developers to push code to directly
• Configure the "promote" pipeline on main branch to deploy the package to prod marketplace
• "promote" pipeline on dev would deploy the package only to pre-prod marketplace
• Versions of packages deployed from dev would have an RC number suffix. Versions of packages deployed from main would not have the RC suffix.