Bug 430822

Changing to proper product/component so the right person can address this issue.

OK, I may have mis-read David's message that I had to do the task, rather than
address it back here.

Talking around, it sounds like the thing we want is to have the component name
changed in the database.  We want old bugs to follow the new component name,
even though there aren't (m)any.  It would be good to not pollute the namespace
with an old unmaintained name.

I made an update in /cvs/docs/owners/owners.list to add this new component
(software-management-guide) with Eric as the maintainer.  I haven't committed
those changes because I don't want to mess anything up.  The entry is in a patch
I'll attach to this report.  Note that I did not erase the entry for
yum-software-management in that patch.

Dave -- would you changing this directly in the db be the best thing?

Oops, forgot to add dkl to the Cc:

Dave - please check this report for comment #2 for you.

thx

Created attachment 294057 [details]
patch to add software-management-guide component

Reassigning.

Dave -- asking around, it sounds as if what we need is for a bugzilla maintainer
to change the component name.

Should I load the proper details in to /cvs/docs/owners/owners.list?  I didn't
want to commit the changes without knowing if that was the right thing to do.

thx - Karsten

(In reply to comment #5)
> Reassigning.
> 
> Dave -- asking around, it sounds as if what we need is for a bugzilla maintainer
> to change the component name.
> 
> Should I load the proper details in to /cvs/docs/owners/owners.list?  I didn't
> want to commit the changes without knowing if that was the right thing to do.
> 
> thx - Karsten

Normally the Fedora Infrastructure team handles all component
adding/editing/removing for the Fedora product in Bugzilla via XMLRPC calls. I
would not be able to comment on the owners.list file myself as I am not involved
with that side of things. I can manually change the component information
throught the UI if you want but their automation may come and change it back if
it is not updated on their end.

Let me know what I need to do
Dave

I don't know of an xmlrpc call that can rename a component.  If there is, I can
make use of it :-)

I think that Karsten understands how docs/owners/owners.list works... he just
needs to coordinate how to go about renaming the product so that it carries all
old bugs over.  Should he commit the changes to owners.list, wait for it to be
created by the Fedora docs scripts, and then have you move the bugs and remove
the outdated component?  Or should he setup a time when you perform a rename of
the component and then he commits the changes to owners.list right afterwards?

(In reply to comment #7)
> I don't know of an xmlrpc call that can rename a component.  If there is, I can
> make use of it :-)
> 
> I think that Karsten understands how docs/owners/owners.list works... he just
> needs to coordinate how to go about renaming the product so that it carries all
> old bugs over.  Should he commit the changes to owners.list, wait for it to be
> created by the Fedora docs scripts, and then have you move the bugs and remove
> the outdated component?  Or should he setup a time when you perform a rename of
> the component and then he commits the changes to owners.list right afterwards?

No the XMLRPC API does not allow for changing of component name yet. This is
planned for 3.2 upgrade in the near future.

I can change the component name through the web UI which will leave all of the
bugs attached to the new name since they are referenced on the back end by ID
and not by name.

I will go ahead and do this.

Dave

I have update the name and changed the default owner to
eric/kwade for any new bugs. To move the old bugs
over to the new owner please use the mass-edit feature of buglist.cgi.

Dave