Build & testing process

The process

The following describes roughly the build & test process of AXP.OS updates:

1. a build id will be defined in the format: YYYY.<id/round> (e.g. 2026.001, see meaning, history & examples)
2. one (1) dedicated AXP.OS Team supported device will be used to test a new update
3. if there are any build or other issues they will be solved for that single device
4. once this device is working, ALL other AXP.OS Team supported devices will be build and build issues solved
5. all devices run through the testing checklist, if there are any issues they will be solved
6. depending on 1-4 one or all devices get re-build and steps repeat from 2(!) again until 5 is without issues. the build id does not change.
7. once this is done all AXP.OS Community supported devices will be build and build issues solved
8. the community goes through the testing checklist, reported issues will be either tracked, solved or documented

That way all devices have the same build id instead of each having unique ones. A build id includes the same set of features regardless how many build runs of a specific device were required to resolve issues.