From owner-freebsd-current  Sun Aug  3 06:40:07 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id GAA24150
          for current-outgoing; Sun, 3 Aug 1997 06:40:07 -0700 (PDT)
Received: from dfw-ix12.ix.netcom.com (dfw-ix12.ix.netcom.com [206.214.98.12])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA24145
          for <current@freebsd.org>; Sun, 3 Aug 1997 06:40:05 -0700 (PDT)
Received: (from smap@localhost)
          by dfw-ix12.ix.netcom.com (8.8.4/8.8.4)
	  id IAA07620; Sun, 3 Aug 1997 08:39:32 -0500 (CDT)
Received: from sjx-ca30-16.ix.netcom.com(204.31.235.176) by dfw-ix12.ix.netcom.com via smap (V1.3)
	id sma007611; Sun Aug  3 08:39:24 1997
Received: (from asami@localhost) by blimp.mimi.com (8.8.6/8.6.9) id GAA01694; Sun, 3 Aug 1997 06:39:20 -0700 (PDT)
Date: Sun, 3 Aug 1997 06:39:20 -0700 (PDT)
Message-Id: <199708031339.GAA01694@blimp.mimi.com>
To: andreas@klemm.gtn.com
CC: current@freebsd.org
In-reply-to: <19970803122321.15396@klemm.gtn.com> (message from Andreas Klemm on Sun, 3 Aug 1997 12:23:21 +0200)
Subject: Re: Make this a relese coordinator decision (was Re: ports-current/packages-current discontinued)
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * So he wanted only to support -stable in the future. But I think
 * this is a step behind.

I perfectly understand that.

 * Figure out, if ports are only made for stable ... If -current
 * does more and more incompatible changes to -stable ... Who
 * should done the fine work of porting perhaps 1250 ports
 * to -current, which will become 3.0-RELEASE and 3.0-STABLE after
 * that ???

That is a very good point, one that I should have mentioned in my
first post.

 * This is not a decision of dropping a pet toy, it is 
 * a decision of a release engineer, who is responsible
 * for the direction of the OS and that a ports collection
 * doesn't get out of sync with everything other than 2.2-STABLE.

The only problem is that there is no "release engineer" that does all
that; Jordan (among others) does the releases, but I build the
packages.  I think what you are saying is closer to David's job (as
the Principal Architect) than Jordan's though.

Satoshi