[BACK]Return to stable.html CVS log [TXT][DIR] Up to [local] / www

Diff for /www/stable.html between version 1.12 and 1.13

version 1.12, 2004/07/26 04:35:10 version 1.13, 2005/01/23 23:36:36
Line 7 
Line 7 
 <meta name="description" content="stable">  <meta name="description" content="stable">
 <meta name="keywords" content="openbsd,anoncvs,updates,stable">  <meta name="keywords" content="openbsd,anoncvs,updates,stable">
 <meta name="distribution" content="global">  <meta name="distribution" content="global">
 <meta name="copyright" content="This document copyright 1996-1998 by OpenBSD.">  <meta name="copyright" content="This document copyright 1996-2005 by OpenBSD.">
 </head>  </head>
   
 <body bgcolor="#ffffff" text="#000000" link="#23238E">  <body bgcolor="#ffffff" text="#000000" link="#23238E">
Line 41 
Line 41 
 <li>Use <b>current source</b> for all of the latest features.  <li>Use <b>current source</b> for all of the latest features.
 </ul>  </ul>
 <p>  <p>
 The <a href="plus.html">Daily Changelog</a> details which post-release  <!-- The <a href="plus.html">Daily Changelog</a> details (amoung other things)
 patches have made it into the patch branch.  As a general principle, all  which post-release changes have made it into the patch branch. -->
   As a general principle, all
 <a href="errata.html">Errata</a> entries will be merged into the patch  <a href="errata.html">Errata</a> entries will be merged into the patch
 branch within 48 hours of when an errata is published.  Other post release  branch within 48 hours of when an errata is published.  Other post release
 patches may be merged in as well, subject to a number of conditions:  patches may be merged in as well, subject to a number of conditions:
Line 72 
Line 73 
 described in the <b>Getting Started</b> section of the  described in the <b>Getting Started</b> section of the
 <a href="anoncvs.html#starting">AnonCVS documentation</a>.  <a href="anoncvs.html#starting">AnonCVS documentation</a>.
 Note that patch branches do not help to upgrade from one release of  Note that patch branches do not help to upgrade from one release of
 OpenBSD to another, e.g. to go from 2.7 to 2.8.  They only provide  OpenBSD to another, e.g. to go from 3.5 to 3.6.  They only provide
 a means for staying up to date with the patches within a given release.  a means for staying up to date with the patches within a given release.
 If you are trying to go from one release to another via source, please visit  If you are trying to go from one release to another via source, please visit
 the <a href="faq/upgrade-minifaq.html">upgrade-minifaq</a>.  the <a href="faq/upgrade.html">upgrade guide</a>.
 Also, you cannot go backwards, from -current back to -stable, because of  Also, you cannot go backwards, from -current back to -stable, because of
 library versioning problems.  library versioning problems.
   
Legend:
Removed from v.1.12  
changed lines
  Added in v.1.13