On Tue, 25 Sep 2007, Garrett D'Amore wrote: > There is another real problem here. I think the only people who are > qualified to "fully" evaluate the bug database are those who are also Sun > employees. Why? Because only they really know what the current bugster > contains, and what features are needed, and what aren't.
I just chopped out a bunch of folks on the cc list. But I wanted to ask, what's the difference anyway? I have seen people complain that they can't read the entire bugs on the OpenSolaris bug database. Ok, even if you could read them internally, there are cases where you still need to look at the actual files to fully understand what is being changed. Hypothetically, let's say you created a process that made it so difficult for engineers to do their putback, that they started to slip changes into another change request to get their changes back? This would never happen at Sun, right? My point is that even if you could read the bug database from outside SWAN, in it's whole, it still wouldn't ensure that you could know exactly what a putback did unless you really looked at every single file and evaluated how they relate to the change request anyway. My $0.02. For the record, I'm not claiming this goes on willy nilly, just that in any large set of sources where you have massive amounts of changes happening on a daily basis, there is a higher chance that engineers will integrate more changes to a CR than logical. Maybe it's a part of common habit. -- Alan DuBoff - Solaris x86 IHV/OEM Group
