From owner-freebsd-python@FreeBSD.ORG  Tue Sep 15 09:57:06 2009
Return-Path: <owner-freebsd-python@FreeBSD.ORG>
Delivered-To: freebsd-python@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E3C3A1065670;
	Tue, 15 Sep 2009 09:57:06 +0000 (UTC)
	(envelope-from david@vizion2000.net)
Received: from dns1.vizion2000.net
	(77-99-36-42.cable.ubr04.chap.blueyonder.co.uk [77.99.36.42])
	by mx1.freebsd.org (Postfix) with ESMTP id 935568FC16;
	Tue, 15 Sep 2009 09:57:06 +0000 (UTC)
Received: by dns1.vizion2000.net (Postfix, from userid 1001)
	id 97E6F34D44F; Tue, 15 Sep 2009 10:57:04 +0100 (BST)
From: David Southwell <david@vizion2000.net>
Organization: Voice & Vision
To: freebsd-ports@freebsd.org
Date: Tue, 15 Sep 2009 10:57:04 +0100
User-Agent: KMail/1.12.1 (FreeBSD/7.2-RELEASE-p3; KDE/4.3.1; amd64; ; )
References: <20090915095154.GH54962@droso.net>
In-Reply-To: <20090915095154.GH54962@droso.net>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <200909151057.04556.david@vizion2000.net>
Cc: re@freebsd.org, miwi@freebsd.org, freebsd-ports-bugs@freebsd.org,
	ports@freebsd.org, portmgr@freebsd.org,
	Erwin Lansing <erwin@freebsd.org>, freebsd-python@freebsd.org
Subject: Re: [HEADSUP]: Ports feature freeze now enforced
X-BeenThere: freebsd-python@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>, 
	<mailto:freebsd-python-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python>
List-Post: <mailto:freebsd-python@freebsd.org>
List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>,
	<mailto:freebsd-python-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2009 09:57:07 -0000

> As an experiment, there will not be a complete ports freeze ahead of the
> release of 8.0.  To ensure that the tree is kept in a stable condition,
> we do need to have more discipline about the feature freeze we are
> currently using.  To achieve this, I have added a new tag to the commit
> log Feature safe: which needs to be set to yes explicitly for each
> commit.  While this is is tedious, it does mean that commits will be
> allowed without prior explicit approval from portmgr.  Portmgr is still
> working on a written set of rules for what is and isn't allowed during a
> feature freeze, so please use common sense for now, and try to err on
> the side of caution and contact portmgr when in any doubt.  Sweeping
> commits touching a large number of ports, shared library updates affect
> more than a trivial number of ports, you get the picture; anything that
> would require a rebuild of more than a trivial amount of ports is not
> allowed without prior approval from portmgr.  With the release only a
> few weeks off, we cannot afford any major mishaps, so be conservative.
> 
> The feature freeze is enforced from right now and current plan is to tag
> the tree after RC1 is released.  There will be a short freeze while the
> tag is processed, and after that we will proceed with the ports slush as
> usual.
> 
> Please consider your commits in this light and help make this experiment
> a success so we can avoid long freezes for future releases.
> 
> -erwin
> 
Please can we ensure the python bug can be fixed. I noiw have a problem 
python26 will not build and the maintainer has not fixed the port. He has not 
tested the routine that causes the failure and a lot of ports are dependent 
upon python26!!

See latest PRs

David Southwell