michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc: update coding guidelines compliance stages

Browse source 
Updates wording in Coding Guidelines page to remove outdated timelines
and correct the criteria for each stage. Changes reflect that we are
in stage 1 and will not reach stage 2 until the CI for enforcing
coding guidelines has been established.

Signed-off-by: Lauren Murphy <lauren.murphy@intel.com>
This commit is contained in:
Lauren Murphy 2021-09-23 18:42:19 -05:00 • committed by Anas Nashif
commit 7ab16c457b
1 changed files with 3 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/contribute/coding_guidelines/index.rst
View file

@ -14,16 +14,14 @@ Stage I
blocked by reviewers/approvers due to violations. blocked by reviewers/approvers due to violations.
Stage II Stage II
Begin enforcement on a limited scope of the code base. Initially this would be Begin enforcement on a limited scope of the code base. Initially, this would be
the safety certification scope. For rules easily applied across codebase, we the safety certification scope. For rules easily applied across codebase, we
should not limit compliance to initial scope. This step requires tooling and should not limit compliance to initial scope. This step requires tooling and
CI setup. CI setup and will start sometime after LTS2.
This stage will begin during the 2.4 development cycle and end with the Zephyr
LTS2 (2.6) to achieve and LTS2 that is ready for certification.
Stage III Stage III
Revisit the coding guideline rules and based on experience from previous Revisit the coding guideline rules and based on experience from previous
stages, refine/iterate on selected rules. This stage is to start after LTS2. stages, refine/iterate on selected rules.
Stage IV Stage IV
Expand enforcement to the wider codebase. Exceptions may be granted on some Expand enforcement to the wider codebase. Exceptions may be granted on some