zephyr/doc/project
Carles Cufi d053b8bf3b doc: Rename stable API change to breaking change
It is often confusing for users and developers alike to see the sentence
"stable API change" in a label or in the release notes. Stable APIs can
change in at least two ways (retaining compatibility or not), and so it
is preferrable to use a term that clearly describes the change as
incompatible, by using the common term "breaking".

Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2023-12-20 09:12:44 -05:00
..
img doc: create new section for project structure 2022-04-07 16:35:19 +02:00
code_flow.rst doc: clarify topic branches 2023-05-17 17:41:37 -04:00
communication.rst doc: communication: update stale info 2023-02-03 20:53:37 +09:00
dev_env_and_tools.rst doc: Rename stable API change to breaking change 2023-12-20 09:12:44 -05:00
documentation.rst doc: create new section for project structure 2022-04-07 16:35:19 +02:00
index.rst doc: create new section for project structure 2022-04-07 16:35:19 +02:00
issues.rst doc: create new section for project structure 2022-04-07 16:35:19 +02:00
lts.svg doc: release process: update milestone definition 2022-04-19 12:26:38 -04:00
milestones.jpg doc: create new section for project structure 2022-04-07 16:35:19 +02:00
milestones2.jpg doc: create new section for project structure 2022-04-07 16:35:19 +02:00
modifying_contributions.rst doc: create new section for project structure 2022-04-07 16:35:19 +02:00
project_roles.rst doc: project roles: Further finetune language 2023-10-27 10:49:47 +02:00
proposals.rst docs: Move RFCs into a separate document 2023-03-06 21:59:23 +01:00
pull_request_classes.png doc: create new section for project structure 2022-04-07 16:35:19 +02:00
release_cycle.svg doc: release process: update milestone definition 2022-04-19 12:26:38 -04:00
release_flow.png doc: create new section for project structure 2022-04-07 16:35:19 +02:00
release_process.rst doc: release process: link to milestone dates on wiki 2023-09-18 11:16:27 +01:00