Date: Wed, 14 Mar 2001 00:56:48 -0800 From: Gregory Sutter <gsutter@zer0.org> To: "=?iso-8859-1?Q?Paul_Richards=F2?=" <paul@originative.co.uk> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: proposals for fixing the PROBLEM at hand Message-ID: <20010314005648.I9369@klapaucius.zer0.org> In-Reply-To: <3AAE5A9A.341F634F@originative.co.uk>; from paul@originative.co.uk on Tue, Mar 13, 2001 at 05:36:26PM %2B0000 References: <20010312160321.B95497@mollari.cthul.hu> <200103130307.TAA41551@gndrsh.dnsmgr.net> <20010312193452.A2927@mollari.cthul.hu> <3AAE5A9A.341F634F@originative.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2001-03-13 17:36 +0000, Paul Richards=F2=0F <paul@originative.co.uk> wro= te: >=20 > I think it'd be much better if -stable became the development branch, > since as far as I'm concerned it's already too unstable for production > use. I can't use -stable ports on my 4.0 live server because there have > been too many architectural changes between 4.0 and 4.3. That's broken > project management and is screwing customers who want to use FreeBSD in There was a lengthy discussion on IRC tonight, in the hope of=20 injecting content into this so-far worthless thread (the only decent thing to come out of it so far has been just pointing out that the problem exists). Here's a quick summary of what was discussed: Proposals: 1. Splitting the upgrade packages into two parts--one to make /usr/ports work, one to make pkg_tools work. obrien suggested this. =20 2. Update the -RELEASE branch for security fixes and critical bugfixes only. The security officer, release engineer, and the security team will be responsible for this, with mandatory approval from the branch maintainer (possibly the release engineer, more likely the security officer) before any commits are made. kris and jkh agreed in principle. An effect of this is to provide a largely-unmoving, yet secure, production platform. If the latest ports are required, the relevant *upgrade.tgz package can be applied. 3. Fix the current broken, unmaintained state of the 4.x upgrade packages. It seems that asami hasn't done any work on these in a long time, and has not produced a working 40upgrade.tgz package. Are there any volunteers to create, repair, and=20 maintain the *upgrade packages? Greg --=20 Gregory S. Sutter Bureaucrats cut red tape--lengthwise. mailto:gsutter@zer0.org=20 http://www.zer0.org/~gsutter/=20 hkp://wwwkeys.pgp.net/0x845DFEDD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010314005648.I9369>