| Stewart Smith | 59d3cb4 | 2018-02-12 11:52:12 +1100 | [diff] [blame] | 1 | .. _versioning: |
| 2 | |
| 3 | Version Scheme |
| 4 | ============== |
| 5 | |
| 6 | Each firmware component has its own versioning scheme, and `op-build` brings |
| 7 | all of these components together in one image with one global version |
| 8 | number. |
| 9 | |
| 10 | Firmware versions are exposed to the user through both the device tree |
| 11 | (:ref:`skiboot:device-tree/ibm,firmware-versions`) and the VERSION firmware |
| 12 | partition. As such, firmware versioning numbers **MUST** follow the |
| 13 | requirements in order for some functionality to be correct. |
| 14 | |
| 15 | skiboot |
| 16 | :ref:`skiboot:versioning` |
| 17 | Hostboot |
| 18 | Currently just uses the git SHA1 of the commit |
| 19 | OCC |
| 20 | Currently just uses the git SHA1 of the commit |
| 21 | Petitboot |
| 22 | Uses a X.Y.Z versioning scheme. |
| 23 | Linux |
| 24 | We use the upstream Linux kernel version, and always append ``-openpowerN`` |
| 25 | where N is a number starting at 1 that increases for each change we make |
| 26 | to any additional patches carried in `op-build` for that specific kernel |
| 27 | version. |
| 28 | We follow the stable tree and have an "upstream *first*" policy in place. |
| 29 | |