Skip to content

Commit

Permalink
stable: clarify stable policy
Browse files Browse the repository at this point in the history
- Not all vXX.0 release trigger stable releases
- Branches are maintained for about 4 years (meaning about 22 branches at any time)

Signed-off-by: Nicolas Morey <nmorey@suse.com>
  • Loading branch information
nmorey committed Oct 8, 2024
1 parent 0498efb commit befe98d
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion Documentation/stable.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,12 +12,16 @@ All bug fixes are to be backported from mainline and applied by stable branch ma

Branched stable releases will append an additional release number (e.g. 15.1) and will ensure that Azure Pipelines CI reports a successful build.

Regular stable releases will be generated at the same time as mainline releases.
Regular stable releases are usually generated at the same time as a mainline release.
Some mainline release are however skipped if not enough significant patches have been queued.
Additional stable releases can be generated if the need arise (Needed by distributions or OFED).
Please contact the maintainer if a stable release is needed outside of the regular schedule.

Stable branches are named stable-vXX where XX is the base version number.
Once older release are no longer supported, their branch will be deleted but the stable release tags will be kept.

Branches are maintained for about 4 years.

## Patch Rules

* It must be obviously correct and tested.
Expand Down

0 comments on commit befe98d

Please sign in to comment.