Skip to content

Commit

Permalink
doc: move "managing a release" from wiki
Browse files Browse the repository at this point in the history
  • Loading branch information
@miri64
miri64 committed Dec 6, 2024
1 parent 5e6e34e commit db53505
Show file tree
Hide file tree
Showing 2 changed files with 302 additions and 0 deletions.
3 changes: 3 additions & 0 deletions doc/doxygen/src/release-cycle.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,8 @@ testing period are back ported from `master` to the release branch and a new
release candidate might be created when a certain milestone is found. If all
major bugs are fixed, the new RIOT release is signed off by the appointed
release manager, usually within 2 weeks after the feature freeze.
More details and instructions for release managers can be found in the
[managing a release guide].

RIOT follows a rolling release cycle, meaning, that support and bug fixes are
only provided for the most current release.
Expand Down Expand Up @@ -55,3 +57,4 @@ if you have RIOT already cloned.

[releases]: https://github.com/RIOT-OS/RIOT/releases
[release specs]: https://github.com/RIOT-OS/Release-Specs
[managing a release guide]: https://github.com/RIOT-OS/RIOT/tree/master/doc/guides/managing-a-release
Loading

0 comments on commit db53505

Please sign in to comment.