Impact evaluation of moving repositories prior to release

Issue Background

In order to pass the license review, one of the requirements is to move the repositories to a subgroup in gitlab.com This has a major impact in our release.

Issue description

Description of the impact of moving the repositories from https://gitlab.com/cip-project/project to https://gitlab.com/cip-project/cip-testing/project

Here's a list of the identified changes necessary:

• Changes to the wiki so that the b@d repos and kernelci-build are correctly located (everywhere p 1, feature page, landing page, check the interesting links list) known issues has links to the issue page for each which will need changing

Changes to be considered

These tasks should be part of other tickets. If they are not, they will be ticketed when they are done. Otherwise, when @toscalix confirms they are part of another release related task:

• amend install_build_script.sh to reference the new location
• change all the issues tickets that relate to the release (or at least some of them!) so they are re-opened (74 86 85 - anymore?)
• test with the new location, build a new vm from scratch
• test vm with qemu and bbb (inc building the bbb kernel)
• update the git repos (including the readme.md we missed last time!)
• create another clean vm for the export box (but I think we can use the above instance?)
• export it, new signings sha256- we'll also need new frontend/backend tar files and to sign / sha256
• test the exported box
• redeclare gold master and reupload the new box/sha/gpg and all the sources
• tag the repos with 0.9.1
• we need to check that no software versions have changed (frontend / backend) and if they have update the features page (diagram may also need changing)

This task blocks #85 (closed)

Acceptance criteria

Once the evaluation is done, @toscalix will define a release plan.