summaryrefslogtreecommitdiffstats
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 11:50:17 +0100
commit55fef35b5c81dd3aeb030edbd609b915e2b27f80 (patch)
tree05bc166dc4a98cb6fe31ed21588780be48a25a97
parent5a6f0efa37c4bfd9ee76f0ed99c16e758449df1e (diff)
downloadmeta-updater-refactor/sumo/rm-implicit-writer.tar.gz
-rw-r--r--CONTRIBUTING.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.adoc b/CONTRIBUTING.adoc
index 73fc3c3..3d0f14d 100644
--- a/CONTRIBUTING.adoc
+++ b/CONTRIBUTING.adoc
@@ -6,7 +6,7 @@ If you are developing with meta-updater, it may be helpful to read the README an
6 6
7== Contributor checklist 7== Contributor checklist
8 8
9* 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. 9* 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.
10* If your change touches platform code (like `classes/sota_<platform>.bbclass`), please check building and updating on this particular platform. 10* If your change touches platform code (like `classes/sota_<platform>.bbclass`), please check building and updating on this particular platform.
11* oe-selftest succeeds. To test meta-updater, run `oe-selftest -r updater` from a build directory with `MACHINE` set to `qemux86-64`. 11* oe-selftest succeeds. To test meta-updater, run `oe-selftest -r updater` from a build directory with `MACHINE` set to `qemux86-64`.
12* 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. 12* 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.