B @ D 0.9 Gold Master declaration
Issue Background
B@D 0.9 Gold Master declaration process.
Issue description
-
Check that the licenses are present in every file of code we have created: AGPLv3 -
Check the license is present in every file of the mirrored repositories -
Sync every repository in gitlab which code is involved in the release. -
Tag every involved repo in gitlab with a release tag on the latest commit. -
Deploy B@D through Vagrant from scratch - Deploy it following the step by step documentation
- Test it
-
Create a box from scratch - Create it, deploy it in a local machine and test it manually
- Ensure that an authentication tool has been added for lava-tool
- Export the box and redeploy the package and test
- Sign the box
-
Create the metadata associated with the box. - Create a tar.gz file with the sources of the code we (Codethink for CIP) have developed.
- Create a tar.gz file with all the lavav2 and kernelci code
- Sign the sources
-
Communicate to the team the Gold Master declaration through mail (not IRC).
Naming and numbering convention are described in #68 (closed)
Acceptance criteria
Once the above process has been followed, the communication of the Gold Master declaration to the team will serve as acceptance criteria.
Edited by username-removed-455007