From owner-freebsd-ports  Fri Nov  8 02:15:11 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id CAA22827
          for ports-outgoing; Fri, 8 Nov 1996 02:15:11 -0800 (PST)
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA22821
          for <ports@freebsd.org>; Fri, 8 Nov 1996 02:15:08 -0800 (PST)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.2/8.6.9) id CAA10258; Fri, 8 Nov 1996 02:14:25 -0800 (PST)
Date: Fri, 8 Nov 1996 02:14:25 -0800 (PST)
Message-Id: <199611081014.CAA10258@silvia.HIP.Berkeley.EDU>
To: obrien@NUXI.com
CC: ports@freebsd.org
In-reply-to: <199611071823.KAA04595@relay.nuxi.com> (obrien@NUXI.com)
Subject: Re: rdist6 port
From: asami@freebsd.org (Satoshi Asami)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * Maybe the core team could post a couple of announcements to
 * freebsd-announce, FBSD usenet newsgroup, etc. stating that 2.2-current is
 * now 3.0-current.  This would give package developers a heads up.

Actually, I recommend porters to make their machines believe they are
still 2.2 (one line change in /sys/conf/newvers.sh) until the release
is out, so we can concentrate on polishing the 2.2R ports tree.

(Of course, ideally we should be on the RELENG_2_2 branch, but it is
lagging pretty far behind in bug fixes right now I don't think I can
run that....)

Satoshi