zephyr/doc/development_process
Alberto Escolar Piedras 52f6f6b960 doc: API lifecycle: Require creating a issue to track removal
As discussed in the TSC meeting of 2019/03/27:
To ensure that we do not forget to remove an API 2 releases later
and to provide a bit better visibility about when the removal
is planned, require that a GH issue be created, and that this
issue be added to the roadmap for the apropriate release.

As a free bonus:
Removed a redundant line in the list and added one missing article.

Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com>
2019-03-31 17:14:56 -04:00
..
api_lifecycle.png doc: Rework Development Process section 2019-02-21 18:04:02 -05:00
api_lifecycle.rst doc: API lifecycle: Require creating a issue to track removal 2019-03-31 17:14:56 -04:00
code_flow.rst doc: fix misspelling in docs and API comments 2019-03-27 15:59:09 -04:00
communication.rst doc: Rework Development Process section 2019-02-21 18:04:02 -05:00
documentation.rst doc: fix docs, include, and Kconfig misspellings 2019-02-28 09:32:12 +01:00
index.rst doc: Rework Development Process section 2019-02-21 18:04:02 -05:00
issues.rst doc: Rework Development Process section 2019-02-21 18:04:02 -05:00
lts.png
merge_window.png
milestones2.png doc: Rework Development Process section 2019-02-21 18:04:02 -05:00
milestones.png doc: Rework Development Process section 2019-02-21 18:04:02 -05:00
proposals.rst doc: Rework Development Process section 2019-02-21 18:04:02 -05:00
pull_request_classes.png doc: Rework Development Process section 2019-02-21 18:04:02 -05:00
release_cycle.png
release_flow.png doc: Rework Development Process section 2019-02-21 18:04:02 -05:00
release_process.rst doc: Update release_process to clarify about GitHub tagging 2019-03-29 10:36:01 +01:00
review_process.rst doc: fix misspelling in docs and API comments 2019-03-27 15:59:09 -04:00