summaryrefslogtreecommitdiffstats
path: root/CONTRIBUTING.adoc
diff options
context:
space:
mode:
authorPatrick Vacek <patrickvacek@gmail.com>2018-10-30 11:48:49 +0100
committerPatrick Vacek <patrickvacek@gmail.com>2018-10-30 13:41:04 +0100
commite9c39a028894b8ed2a38a922d5f905a42985aeb4 (patch)
treef359b071641c052e95fd582eb9ae36e7fcce5f9e /CONTRIBUTING.adoc
parentc18824081b5d9d01337b3e33f5c78368b7fcf97b (diff)
downloadmeta-updater-e9c39a028894b8ed2a38a922d5f905a42985aeb4.tar.gz
Diffstat (limited to 'CONTRIBUTING.adoc')
-rw-r--r--CONTRIBUTING.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.adoc b/CONTRIBUTING.adoc
index cd6e981..8f63245 100644
--- a/CONTRIBUTING.adoc
+++ b/CONTRIBUTING.adoc
@@ -14,7 +14,7 @@ If you are developing with meta-updater, it may be helpful to read the README an
14 14
15== Contributor checklist 15== Contributor checklist
16 16
17* OTA-enabled build succeeds at least for one platform, the resulted image boots, and an update can be installed. This check is absolutely necessary for every pull request unless it only touches documentation. 17* OTA-enabled build succeeds for at least one platform, the resulting image boots, and an update can be installed. This check is absolutely necessary for every pull request unless it only touches documentation.
18* If your change touches platform code (like `classes/sota_<platform>.bbclass`), please check building and updating on this particular platform. 18* If your change touches platform code (like `classes/sota_<platform>.bbclass`), please check building and updating on this particular platform.
19* oe-selftest succeeds. To test meta-updater, run `oe-selftest -r updater` from a build directory with `MACHINE` set to `qemux86-64`. 19* oe-selftest succeeds. To test meta-updater, run `oe-selftest -r updater` from a build directory with `MACHINE` set to `qemux86-64`.
20* Updates are forwards- and backwards-compatible. You should be able to update an OTA-enabled build before the change is applied to the version with change applied and vice versa. One should pay double attention to the compatibility when bootloader code is affected. 20* Updates are forwards- and backwards-compatible. You should be able to update an OTA-enabled build before the change is applied to the version with change applied and vice versa. One should pay double attention to the compatibility when bootloader code is affected.