This is an old revision of the document!
OPNFV Process to prepare the release
This page describes the steps to prepare the Arno release.
For later releases there will be a different process.
Steps to take for Release
Based on input from BGS and FuncTest, TSC decides on
Based on the decision of TSC, Octopus identifies/extracts the SHA1s for the repos genesis and functest from Jenkins build/deploy/test jobs.
Octopus identifies SHA1s for the repos pharos, octopus, opnfvdocs, and releng and confirms them with respective PTLs.
Octopus provides git instructions to PTLs in order to apply tags.
PTLs tag corresponding/identified revisions/SHA1s in all the repos that are part of the release with agreed tag. (genesis, functest, pharos, octopus, opnfvdocs, releng)
PTLs create maintenance branch in all the repos for the projects that are participating in Arno.
(Instructions will be provided by Octopus).
Octopus team run final deploy and verify on the release revision.
Once validated LF copies the final artifacts and documents to Arno release storage (see below):
-
Marketing team send release announcement mail.
Release Tag
Maintenance Branch
Storage Locations for Final Artifacts
git instructions
Committers will apply the tags to the genesis, octopus, releng*, pharos, functest and opnfvdocs repos and create branches for maintenance.
Repo | SHA1 | Tag/Branch Status |
genesis | 321aff9 | |
functest | 3af6557 | Done |
pharos | cdf8591 | Done |
opnfvdocs | 9d00c5d | Done |
octopus | 4da0ef5 | Done |
releng | 305051a | Done |
Tagging
Please get the SHA1 for your project from the table above.
Please contact aricg and/or other Octopus members on #opnfv-octopus channel if you experience any issues.
Branching
Please get the SHA1 for your project from the table above.
Please contact aricg and/or other Octopus members on #opnfv-octopus channel if you experience any issues.
Please note that releng won't be branched off.