Create a first release

[kimwnasptd]

This issue aims to organise all the steps we want to make to have a first release in this repo. This is a sub-part of the whole migration #74, as the migration covers other parts like issues migration.

To have the first release, in my mind, we need to work on the following:

1. Define first release artifacts and branches #118
2. Ensure we have fixed the bugs in our CI:
   1. Integration tests don't get triggered by components they rely on #119
   2. Testing helper scripts are not executable #120
   3. Define testing objects in separate files #121 (good to have)
3. Update images to use agreed registries #122
4. Create automation script for updating manifests #123
5. Create release branch and update VERSION and used tags #124

The first one is the only process discussion we'll have, but IMO all the others can happen in parallel.

I'd suggest though that we tackle them in that order, as we are now seeing the CI bugs bite us in different places, i.e. #115 (comment)

cc @juliusvonkohout @thesuperzapper @andyatmiami @kunal-511

[juliusvonkohout]

CC @tarekabouzeid

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed if no further activity occurs.
Thank you for your contributions.

Members may comment /lifecycle frozen to prevent this issue from being marked as stale.

[andyatmiami]

/lifecycle frozen

[kimwnasptd]

To everyone following this thread, the remaining items are:

1. To merge test: Reorganize testing structure  #133
2. Cut the branches and ensure the CI is publishing as expected (we can try with a test tag initially)

Note that if the review of the refactored CI will take too long then we can continue on without it. But let's aim to have it.

cc @juliusvonkohout @andyatmiami @akagami-harsh @andreyvelich

[kimwnasptd]

It would also be ideal to have this one #154 but let's see how we'll progress