| commit | 05626e1319b22ae646de10aeb5b2171e4510501c | [log] [tgz] |
|---|---|---|
| author | Maarten Derks <maarten@fairphone.com> | Mon Oct 04 10:35:34 2021 +0200 |
| committer | Maarten Derks <maarten@fairphone.com> | Mon Oct 25 14:10:05 2021 +0200 |
| tree | 53a73f4e28d0c80349414458dacf9e5f36e03929 | |
| parent | c2988748ea0d181cc09dbfb5088844efb908a543 [diff] |
Checkup release 20202, version 2.2.2 Issue: CHK-43 Change-Id: I2adc78afbbff087f985185c0511974a0e16241e9 (cherry picked from commit 049ff1f29157a92bf62cceeb32a41f74af94550b)
An Android app that allows end users to test the features of their Fairphone 2.
Note: This branch (prebuilts) only contains prebuilts, check out master for the up-to-date development branch. Make sure to have a look at the documentation there, it explains the development workflow.
Releasing a new version happens at the code level. We now use a prebuilt approach to have a shared release between the different operating system flavours running on the Fairphone 2. This approach also allows for OTA updates through app markets.
The prebuilts branch versions the official build artifacts from a named release (in the form of prebuilts-X.Y.Z), signed with the widely known Fairphone key. They match a source code release (release-X.Y.Z) (from the master branch).
Updates to prebuilts take the form of prebuilts-X.Y.Z-MR_N_ where N is a natural number denoting the update number. Such updates can only happen if the change is limited to the build system. If a source code change is needed, its version cannot be maintained and thus a new release is required.
Note: There is only one release supported at a given time, hence using a single branch to version the prebuilts artifacts is not an issue.
FIXME: The prebuilts tags should be signed by the build system.