B@D v1.0 release: Gold Master declaration

Issue Background

Once LAVA has been updated and initramfs can be built, it is time to release. We will not update kernelCI to the latest version since there are complex issues with that version and as there are soon to be other changes we would prefer something more stable for the release/training at ELC-E.

Issue description

• Licenses conformance.

  • This task is developed in #140 (closed) since there are new tasks to perform towards full GPL compliance according to OpenChain standards

• Sync every repository in gitlab which code is involved in the release (except those frozen).

  • KernelCI backend
  • kernelci frontend
  • kernelci build
  • KernelCI backend config
  • kernelci-front-end-config.

• Tag every involved repo in gitlab with a release tag (v1.0) on the latest commit.

  • board-at-desk-single-dev
  • KernelCI backend
  • kernelci frontend
  • kernelci build
  • KernelCI backend config
  • kernelci-front-end-config.

• Deploy B@D through Vagrant from scratch

  • Deploy it following the step by step documentation
  • Test it
  • Ensure that an authentication tool has been added for lava-tool
    • Test with lava-tool

• Exporting the box

  • Create it, deploy it in a local machine and test it manually
    • In a machine with Linux as host OS
    • In a machine with Windows 10 as OS

• Create the metadata associated with the box.

  • Create a tar.gz file with the sources of the code we (Codethink for CIP) have developed, from gitlab.
  • Create a tar.gz file with all the lavav2 and kernelci code from gitlab.

• Sign what will be released

  • The sources
  • The box
  • The metadata

• Communicate to the team the Gold Master declaration through mail (not IRC).

Naming and numbering convention are described in #68 (closed)

Acceptance criteria

• Link to the communication of Gold Master declaration.
  • @toscalix : "I put here the public communication since there is no point in adding the link to an restricted access mailing list archived mail."