Skip to content

Commit 7ab16c4

Browse files
laurenmurphyx64nashif
authored andcommitted
doc: update coding guidelines compliance stages
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 <[email protected]>
1 parent 05f2050 commit 7ab16c4

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

doc/contribute/coding_guidelines/index.rst

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,16 +14,14 @@ Stage I
1414
blocked by reviewers/approvers due to violations.
1515

1616
Stage II
17-
Begin enforcement on a limited scope of the code base. Initially this would be
17+
Begin enforcement on a limited scope of the code base. Initially, this would be
1818
the safety certification scope. For rules easily applied across codebase, we
1919
should not limit compliance to initial scope. This step requires tooling and
20-
CI setup.
21-
This stage will begin during the 2.4 development cycle and end with the Zephyr
22-
LTS2 (2.6) to achieve and LTS2 that is ready for certification.
20+
CI setup and will start sometime after LTS2.
2321

2422
Stage III
2523
Revisit the coding guideline rules and based on experience from previous
26-
stages, refine/iterate on selected rules. This stage is to start after LTS2.
24+
stages, refine/iterate on selected rules.
2725

2826
Stage IV
2927
Expand enforcement to the wider codebase. Exceptions may be granted on some

0 commit comments

Comments
 (0)