Hi Terry- Brendan gave us permission to rename Mozilla product to MozillaClassic and create a new product called Browser. I have spent the last two days contacting engineers to ensure that you get one set of info for all the changes needed. This is ready (except for a few decription and QA Contacts) and located at: http://slip/projects/mozilla/MozillaBugzillaUpdates.html You may want to do this big change early in am (now) or at night. Your call. Please let me know if you have any questions. I tried to be very clear in this info table.

Let me make sure I have this straight, because it seems more complicated than I thought it was going to be. I am to: - Create a new product called Browser. - Take several (I count 17) components that are currently in Mozilla, make identical components in Browser, move the bugs that are assigned to them over to Browser, and then remove those components from Mozilla. - Take another 9 components in Mozilla, and blow them away entirely (first checking that there are no bugs assigned to them!) - Create 15 new components in Browser. - Rename Mozilla to MozillaClassic - Ensure that no new bugs ever end up in MozillaClassic. (Do you think I should allow existing bugs to be moved into MozillaClassic)? - Leave NGLayout as it is. Does that seem like a correct summary?

Answers*: - Create a new product called Browser. *YES. - Take several (I count 17) components that are currently in Mozilla, make identical components in Browser, move the bugs that are assigned to them over to Browser, and then remove those components from Mozilla. *YES. I count 17 also. Will be 18 with Apprunner. - Take another 9 components in Mozilla, and blow them away entirely (first checking that there are no bugs assigned to them!) * YES. But I count 7 to totally blow away. Internationalization and Localization should stay as components showing in Browser(now all in NG Layout bugs) and Mail/News, but no longer show up in as MozillaClassic component. - Create 15 new components in Browser. *YES. - Rename Mozilla to MozillaClassic *YES. - Ensure that no new bugs ever end up in MozillaClassic. (Do you think I should allow existing bugs to be moved into MozillaClassic)? *YES. I will need to query for open bugs in that product to make sure they all get moved to the right place. But no new bug entry should be allowed. - Leave NGLayout as it is. *NO. Spoke with NGLayout guys and they said...move our components under Browser product. But ya know, let me check with them on this one, one more time to make sure. Could you do all but the last step whilst I check? Hope this table made it easier for you. I'll get more descriptions as we go.

I am going to rename the "Security - xxx" component to just be "Security". No other component has a codename in it. And I don't want to get visited by South Park lawyers.

I would prefer to do this as all one giant step. (I have almost finished writing the script that will do the magic.) I don't want to do NGLayout->Browser as a separate step, so I will wait until I get a definitive answer as to what to do there.

You made me laugh :-) Yeah, good idea. I quit watching a while ago...who ever did kill Kenny?

OK, the deed is done. (Whomp!)

Most excellent! Marking Verified.

Moving to Bugzilla product

moving bugzilla.mozilla.org database bugs from bugzilla prodcut to mozilla.org