Lines Matching refs:stable

10 The stable releases go on to a branch like v4.0-stable as described below, over
13 into your planning that you will need to follow v4.0-stable in order to stay on
16 And we only backport fixes to the last stable release, although we will make
57 to be working, it's copied out into a versioned stable branch, like `v3.0-stable`.
59 ![stable branches are copied from master](../doc-assets/lws-relpol-2.svg)
72 that was copied to form the last -stable branch.
74 In that case, the patch may be backported to the last stable branch to also fix
83 When new stable releases are made, the soname is bumped reflecting the API is
86 ![backports from master to stable](../doc-assets/lws-relpol-3.svg)
96 Periodically fix patches pile up on the -stable branch and are tagged out as
97 "point releases".  So if the original stable release was "v3.0.0", the point
100 ![point releases of stable](../doc-assets/lws-relpol-4.svg)
109 ![backport to multiple stable branches](../doc-assets/lws-relpol-5.svg)
121 Since stable branches don't allow new features, they are run as traditional trees