From owner-freebsd-ports Sat Sep 21 0:20:56 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0D5037B401; Sat, 21 Sep 2002 00:20:54 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-165-226-88.dsl.lsan03.pacbell.net [64.165.226.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69A4443E3B; Sat, 21 Sep 2002 00:20:54 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 59D2C66B28; Sat, 21 Sep 2002 00:20:50 -0700 (PDT) Date: Sat, 21 Sep 2002 00:20:50 -0700 From: Kris Kennaway To: ports@FreeBSD.org Subject: HEADS UP: Ports tree is now frozen Message-ID: <20020921072049.GA18978@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline The ports tree is now frozen. As explained in my previous email announcing the freeze, in contrast to previous releases we will not be laying down the release tag immediately, and the freeze will not be enforced by CVS avail permissions. This means it's UP TO YOU to restrain yourself from committing without authorization during the freeze. I expect committers to take this seriously, and I do not want to have to back out any unapproved commits. Here are the rules of what will and will not be allowed during the freeze. Print them out and stick them to the wall/your forehead/whatever you need to do to make sure you follow them :-) * Fixing a build error listed on bento or beta does not require portmgr@ permission (except for fixing an error by upgrading the port to a newer version) * Fixing an error not listed on bento or beta (e.g. a runtime error, or fixing broken port behaviour) requires permission from portmgr@ (explain the problem and provide your *fully tested* patch). * No port upgrades without permission from portmgr@ * No port removals without permission from portmgr@ * No new ports, except in special circumstances (i.e. not "I forgot to do it before now") and with permission from portmgr@ * No breaking ports without permission from portmgr@ :-) * If in doubt, ask portmgr@ The ports freeze will last for a week or so, depending on how the rest of the release process goes (the published timeline is kind of tight). I strongly encourage all ports committers and maintainers to spend this time fixing some of the hundreds of broken ports currently in the ports collection, and to test existing ports and packages. Note that the PR database already contains fixes for many of these ports; I'd like to see as many of those committed as possible. Kris On behalf of portmgr --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9jB3QWry0BWjoQKURAgE/AJ9yoZmx0BSoqSqeanwo9xJLzhI/YgCfdTIT OmXpC3S0d6pugOJJqGs+JFE= =SF9E -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message