On Fri, 26 Oct 2007, timeless wrote: > On 10/26/07, Valerie Bubb Fenwick <[EMAIL PROTECTED]> wrote: >> Obviously someone needs to be looking after the community, or the >> bugs will be entering a black hole. > > I'm working on trying to recover another project from this black hole, > I know Sun is much less at risk from this than we are, but it can > happen (and believe me you don't want to go there).
Even at sun, we sometimes have bug subcategories go into a black hole. It is tricky, but we do try to fix it when the issues are found. > I wrote: >> Note that in the Bugzilla's with which I work, the QA field is just a >> watchable entity, but that's different from claiming the entity is >> responsible for anything, in fact it's about as close as saying that >> no one in particular is responsible for it. > > On 10/26/07, Valerie Bubb Fenwick <[EMAIL PROTECTED]> wrote: >> No data, but there are nearly daily requests. Sometimes more. > > I'm partly trying to understand how much time is devoted to this work, > and whether we're trying to streamline it or just reproduce it > (I don't mind either way, since you seem comfortable with it). There are two aspects of the work. Managing the namespace, ie new categories & subcategories and new release/build values, which is done by me & Scott Rotondo for product solaris. Then there is the actual work for the database changes. I don't do that - someone from ITops does. They do all of the changes we approve, as well as all of the changes for default RM & IE values. The actual database maintenance is a lot more time consuming than approving major changes. I could ask one of our reps to get some actual data (I'm pretty sure they log how much time they spend on these "trouble" tickets). Rachna? >> Lots of changes, like changing RM (responsible manager) or >> IE (initial evaluator) do not require approval, but I see the changes. > > Interesting, is this a useful feature (it's essentially a form of logging), > are there times when you've needed to react to this? Yes, indeed. We've found that sometimes new techs add things into the database that we did not approve, and sometimes we need to take action to get it removed (sometimes it's okay). Not too long ago a new tech deactivated everything under "solaris/network" - and the email auditing alerted me to that, so we could get it fixed over the weekend before really anyone was impacted. >> So, I'd say in solaris we probably see at least one category or >> subcategory change about 5 times a week. > > Wow, would it help if categories could have people responsible for > making changes within their category (and not capable of making such > changes outside)? Or are you relying on yourself to make sure the > overall bigger picture is maintained? Like I said before, we just oversee the namespace in general of the "product" in BT2. we don't, typically, actually file trouble tickets. Little change requests, that do occur often, like chnage in IE, can be done by anyone. (only the database administrators can make the actual changes). So, the work is distributed. Valerie -- Valerie Fenwick, http://blogs.sun.com/bubbva Solaris Security Technologies, Developer, Sun Microsystems, Inc. 17 Network Circle, Menlo Park, CA, 94025. 650-786-0461 _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
