Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 13 Oct 2013 03:14:32 -0500 (CDT)
From:      Nathan Whitehorn <nwhitehorn@anacreon.physics.wisc.edu>
To:        Devin Teske <dteske@FreeBSD.org>
Cc:        "src-committers@freebsd.org" <src-committers@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "Teske, Devin" <Devin.Teske@fisglobal.com>, Nathan Whitehorn <nwhitehorn@freebsd.org>, "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>, =?ISO-8859-15?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no>
Subject:   Re: svn commit: r256343 - in head/usr.sbin/bsdinstall: . scripts
Message-ID:  <alpine.BSF.2.00.1310130255190.33798@anacreon.physics.wisc.edu>
In-Reply-To: <13CA24D6AB415D428143D44749F57D720FC5B8F1@LTCFISWMSGMB21.FNFIS.com>
References:  <201310112041.r9BKfZeT002056@svn.freebsd.org> <5258F9B3.7030101@freebsd.org> <13CA24D6AB415D428143D44749F57D720FC5B547@LTCFISWMSGMB21.FNFIS.com> <86txgmr0oh.fsf@nine.des.no> <13CA24D6AB415D428143D44749F57D720FC5B8F1@LTCFISWMSGMB21.FNFIS.com>

next in thread | previous in thread | raw e-mail | index | archive | help


On Sat, 12 Oct 2013, Teske, Devin wrote:

>
> On Oct 12, 2013, at 8:03 AM, Dag-Erling Sm?rgrav wrote:
>
>> "Teske, Devin" <Devin.Teske@fisglobal.com> writes:
>>> The code to replace the use of camcontrol is a a *very* complex parsing
>>> of the geom XML configuration data stashed in sysctl. jmg@ started the
>>> ball rolling on that.
>>
>> You realize there is a text version as well?
>>
>>> Yes. Which has been discussed at-length, you didn't need to put a
>>> sandbag on my back (publicly no less; thanks for that).
>>
>> Umm, I think Nathan was pretty civil.  You're the one who's turning this
>> into a catfight.
>>
>
> Reflecting upon the thread to see if you're _right_...
>
> 1. He stated there were still some issues. [definitely civil]
> 2. "I am surprised you committed it especially to stable/10,
> before those issues were resolved." [civil? or inflammatory?]
> 3. "I'm also not sure if people can review their own patches." [misunderstanding]
> 4. "Installer regressions are very easy to introduce and very problematic
> when created." [statements like that invariably lead people to believe he views
> the commit as a regression -- I explained in a follow-up that it is not a regression]
> 5. "Real review for installer changes is thus especially important this late in the
> release cycle." [I read this invariably as he views that the commit did not go
> through "Real review", but again... there is no regression and it's purely value-
> add]
> 6. "Do you have any plans to fix these issues in the very near future?" [definitely civil]
>
> What got me ralled up was #'s 2, 4, and 5.

Hi Devin --

I'm sorry you felt I was attacking you. I was, as I said, very glad to see 
someone work on ZFS support in the installer. The patch seems to have only 
minor issues, most of which were identified earlier. You will note 
that I am asking you to fix them, but not for a backout, and for you (and
everyone else) to ask for review for future non-trivial installer patches,
just as you would for changes to any discrete unit of the operating system.
With respect to the patch itself, there are a few other architectural things
that need to be fixed: the man page needs updating, you did not update the
part of the installer that does unattended installations, etc.

The end comment was not to say that this patch *is* a regression -- it 
clearly isn't since it adds a new feature and doesn't touch existing ones 
-- but a general comment that the installer is sensitive to them. Unlike 
most parts of the system, it is run only rarely (developers updating their 
systems from SVN don't reinstall them from media) and is simultaneously 
the first thing and, until recently, the *only* thing, new users see when 
they first download FreeBSD. So bugs can easily not be found but, when 
they are found, totally cripple all other features of the operating 
system since it can't be installed for anything else to even be used.
Similar things can be true for things that are not quite regressions (new 
features that don't work as advertised, typos in menus) since the chance 
we notice them is very low while the chance new users do is high.

This is why the review requirements, and testing times, for installer 
changes are typically quite high. This is especially true in the run-up to 
a release.
-Nathan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1310130255190.33798>