This is an old revision of the document!
Table of Contents
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.
Arno SR1 Release
Steps to take for SR1 Release
- Based on input from BGS and FuncTest, TSC decides on
- The exact version of ISO, deploy and test scripts and documents to use in the release
- The release tag name
- 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)
- 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):
- LF creates links to released artifacts and documents on download pages: www.opnfv.org/software/download
- Marketing team send release announcement mail.
SR1 Release Tag
arno.2015.2.0
SR1 Maintenance Branch
stable/arno (this branch already exists)
Storage Locations for Final SR1 Artifacts
PELIMINARY
-
-
- source file:needs to be created manually and stored
-
-
-
-
- source file:needs to be created manually and stored
-
-
-
- source file:http://artifacts.opnfv.org/genesis/arno/common/docs/user-guide.pdf (no change)
-
-
- source file:http://artifacts.opnfv.org/pharos/docs/pharos-spec.pdf (no change)
-
SR1 git instructions
Committers will apply the tags to the genesis, octopus, releng*, pharos, functest and opnfvdocs repos.
SHA1s to Apply Tags on for SR1
SR1 Tagging
- git fetch origin
- git checkout <SHA1>
- git tag -am "arno.2015.2.0" arno.2015.2.0
- git push origin arno.2015.2.0
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.
Arno Release
Steps to take for Release
- Based on input from BGS and FuncTest, TSC decides on
- The exact version of ISO, deploy and test scripts and documents to use in the release
- The release tag name
- 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):
- LF creates links to released artifacts and documents on download pages: www.opnfv.org/software/download
- Marketing team send release announcement mail.
Release Tag
arno.2015.1.0
Maintenance Branch
stable/arno
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.
SHA1s to Apply Tags and Create Branches on
(you can get the SHA1 listed, e.g. with "git show-branch –sha1-name")
| Repo | SHA1 | Tag/Branch Status |
|---|---|---|
| genesis | 321aff9 | Done |
| functest | 3af6557 | Done |
| pharos | cdf8591 | Done |
| opnfvdocs | 9d00c5d | Done |
| octopus | 4da0ef5 | Done |
| releng | 305051a | Done |
Tagging
- git fetch origin
- git checkout <SHA1>
- git tag -am "arno.2015.1.0" arno.2015.1.0
- git push origin arno.2015.1.0
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
- Click the link for your project from below list
- Fill in the boxes as shown below
- Branch Name: stable/arno
- Initial Revision: <SHA1>
- Click "Create Branch"
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.
