Added informations relevant to maintainers on how the normal review process
differs during the feature freeze, or when the are targeting a release rather
than the master branch.
Updated the link to the coding conventions in CONTRIBUTING.md and MAINTAINING.md
to no longer point to the wiki, but to CODING_CONVENTIONS.md in the RIOT
repository.
During RIOT Summit 2018 the attending maintainers found that the
organization for the review process involving multiple maintainers is
lacking both in process description and existing mechanisms.
This changes the "Organisation of reviewing between maintainers"
section of the maintenance guidelines, to be in accordance with the
results of the discussions spawned from this fact.
If approved the following labels are added to GitHub:
- Reviewed: 1-fundamentals
- Reviewed: 2-code-design
- Reviewed: 3-testing
- Reviewed: 4-coding-conventions
- Reviewed: 5-documentation
- This document is the result of original work by @haukepetersen and
refinement by @miri64, @aabadie, @kaspar030, @jcarrano,
@PeterKietzmann, @ZetaR60, and @jia200x.
