+ Any commit in Linus's tree can be nominated by mail to this list, if it
+ meets the criteria - see
+ <a href="http://www.kernel.org/doc/Documentation/stable_kernel_rules.txt"><tt>Documentation/stable_kernel_rules.txt</tt></a>
+ </li>
+ <li>
+ Occasional regression fix in stable without a corresponding
+ commit in Linus's tree, because the change that regressed was
+ OK in mainline
+ </li>
+ </ul>
+</div>
+
+<div class="slide">
+ <h1>The stable update process (2)</h1>
+ <ul>
+ <li>
+ Maintainer sends pending changes to mailing list, original
+ authors, etc., for time-limited review and testing
+ <ul>
+ <li>
+ Fix might not be needed in a stable branch, or might not
+ work due to missing dependencies
+ </li>
+ <li>
+ Fix might have been found to introduce a regression in
+ mainline, so must wait until second fix available
+ </li>
+ </ul>
+ </li>
+ <li>
+ Maintainer drops/adds changes based on review, then applies
+ to stable branch and tags release
+ </li>
+ <li>
+ 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
+ and other news media
+ </li>
+ </ul>
+</div>
+
+<div class="slide">
+ <h1>Distributions and stable updates</h1>
+ <ul>
+ <li>
+ Package maintainers want to get bug fixes without waiting for
+ the next release - particularly for security
+ </li>
+ <li>
+ Maintainers report bugs upstream, find and sometimes write
+ fixes, and stable updates are a way to share these fixes across
+ distributions