<h1>The stable update process (2)</h1>
<ul>
<li>
- Stable branch maintainer sends pending changes to the mailing
- list, the original authors, etc., for a time-limited period of
- review and testing
+ Maintainer sends pending changes to mailing list, original
+ authors, etc., for time-limited review and testing
<ul>
<li>
- Although the changes have been accepted by Linus, some might
- not be needed in a stable branch or might not work due to
- missing dependencies
+ Fix might not be needed in a stable branch, or might not
+ work due to missing dependencies
</li>
<li>
- A fix might have been found to introduce a regression in
- mainline, so should only be applied to the stable branch
- along with a second fix for the regression
+ Fix might have been found to introduce a regression in
+ mainline, so must wait until second fix available
</li>
</ul>
</li>
<li>
- All changes that passed review (and maybe some that were
- added) are applied to the stable branch and the release is
- tagged
+ Maintainer drops/adds changes based on review, then applies
+ to stable branch and tags release
</li>
<li>
- Greg pushes the tag to kernel.org (possibly after pulling
- from the other maintainer) which generates tarballs,
- updates the front page, etc.
+ Greg pushes tag to kernel.org (possibly after pulling from
+ another maintainer) which generates tarballs, updates the front
+ page, etc.
</li>
<li>
Maintainer announces the release, shortly followed by LWN