Date: Mon, 9 Mar 2009 20:38:10 -0500 From: Mark Linimon <linimon@lonesome.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: Stanislav Sedov <stas@FreeBSD.org>, svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, Andrew Thompson <thompsa@FreeBSD.org> Subject: Re: svn commit: r189594 - head Message-ID: <20090310013810.GC22633@lonesome.com> In-Reply-To: <20090309222705.GA49870@troutmask.apl.washington.edu> References: <200903091922.n29JMjLR035306@svn.freebsd.org> <20090309194338.GA48593@troutmask.apl.washington.edu> <20090309195805.GA53225@citylink.fud.org.nz> <20090309222705.GA49870@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 09, 2009 at 03:27:05PM -0700, Steve Kargl wrote: > When Mark Linimon, a member of portmgr, posts on Feb 26th > > (http://lists.freebsd.org/pipermail/freebsd-ports/2009-February/053282.html > > There appears to be a disconnect with USB2 development and the > rest of FreeBSD. Within 2 days after posting that, we had a list created of all the ports the ports that were broken by known commits to -current, and people started working through them. I am very encouraged by the response. In theory, there would be enough volunteers and spare machines to regression-test every change that might be disruptive before commit. In practice, it's simply not possible. As it is, since 7.1 went out the door we (portmgr) have been continually running -exp runs to try to work through our backlog. We have several more in the queue that are also high priority. (In particular, we spent time on the xorg upgrade, which we knew would affect all users, not just -current). I suppose portmgr could have objected to the merge -- but note, it had been in the planning stage for quite some time, and the window to get this massive change into the src base before 8.0 was starting to close. Now that the commit has gone in, all we can do is ask people to help in fixing problems. In this, I think we could hardly have done better. As mlaier has pointed out, -current has sharp edges. It's one of 3 choices open to you, the other two being -stable (which will still have ports regressions from time to time -- see xorg -- and sometimes even src regressions), and a release, which is the best we can do with respect to QA. If you can't deal with having your system out of commission on occasion, then -current isn't for you. mcl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090310013810.GC22633>