===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/Attic/ports.html,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -r1.58 -r1.59
--- www/Attic/ports.html	2001/09/10 19:26:32	1.58
+++ www/Attic/ports.html	2001/10/06 14:00:36	1.59
@@ -174,31 +174,10 @@
 
 <p>
 The ports tree, like the rest of OpenBSD, is constantly changing.  
-The normal life cycle of the ports tree is as follows:
-<ul>
-<li>Track the latest release of OpenBSD for a few months after the release
-comes out.
-<li>Switch to tracking OpenBSD-current about two months before the next
-release.
-</ul>
-The change of status will be widely publicized on the 
-<a href=mail.html>mailing lists</a>. As of OpenBSD 2.9, the ports
-tree also gets tagged before the switch. If you're running a <i>stable</i>
-system, you can update to the last `correct' experimental ports tree that
-works on your system as follows:
-<pre>
-	# <strong>cvs -q up -rOPENBSD_2_9_TRACKING_SWITCH -P ports</strong>
-</pre>
-For definitions of <i>current</i> and <i>stable</i>, see the 
-<a href="faq/upgrade-minifaq.html#1.1">Upgrade 
-Mini-FAQ</a>.
-
 <p>
 The current ports tree <strong>may not</strong> be used with the previous
-release once the switch to tracking OpenBSD-current occurs.  This is due
-to changes, typically with the port make process, that require code
-based upon the OpenBSD-current source tree. This switch will be announced
-on the <a href="mail.html"><tt>ports@openbsd.org</tt> mailing list</a>.
+release.  This is due to changes, typically with the port make process, 
+that require code based upon the OpenBSD-current source tree. 
 <p>The ports tree works as a single entity. Updating a single directory is
 not guaranteed to work, as package dependencies may force you to update
 and recompile vast portions of the ports tree.
@@ -208,6 +187,23 @@
 <code>ports-changes@openbsd.org</code> or
 <code>tech@openbsd.org</code> will probably be invaluable.
 
+<p>You are advised to track ports-stable on a production machine:
+we will try to keep the stable ports tree up-to-par with respect to
+problems, and to provide timely binary updates as well.
+
+<p>Note that vanishing distfiles is not an issue, as
+ftp.openbsd.org holds the complete repository. Even changing checksums is
+not an issue: you can issue the command
+<pre>
+	make checksum REFETCH=true 
+</pre>
+to make sure you are grabbing the correct distfile for your ports tree.
+
+For definitions of <i>current</i> and <i>stable</i>, see the 
+<a href="faq/upgrade-minifaq.html#1.1">Upgrade 
+Mini-FAQ</a>.
+
+
 <p>A list of <a href="portsplus/index.html">daily changes</a> to ports
 and ports-current is available.
 
@@ -383,6 +379,6 @@
 <hr>
 <a href="index.html"><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a> 
 <a href="mailto:www@openbsd.org">www@openbsd.org</a>
-<br><small>$OpenBSD: ports.html,v 1.58 2001/09/10 19:26:32 jufi Exp $</small>
+<br><small>$OpenBSD: ports.html,v 1.59 2001/10/06 14:00:36 espie Exp $</small>
 </body>
 </html>