BMO Reorg Plan
--------------

Do the following things, mostly in order (but see "Timing" at the end):

1) Create new classifications using GUI:
   Graveyard (Description: "Old, retired products", sort key: <last>)

2) Rename classifications using GUI:
   Client Support to Other

3) Move products between classification using GUI:
   Grendel from Client Software to Graveyard
   CCK from Unclassified to Graveyard
   Derivatives from Unclassified to Graveyard
   MozillaClassic from Unclassified to Graveyard
   UI: "reclassify" link from the top-level classification list

4) Create new products using GUI:
   Core Graveyard in Graveyard 
     (desc: "Old, retired Core components", closed for entry, no charts)
   MailNews Core in Components
     (desc: "Mail and news components common to Thunderbird and SeaMonkey",
      open for bug entry, create charts)

5) Rename products using GUI, and fix queries using fixqueries.pl:
   Mozilla Application Suite to SeaMonkey
   Sumo to support.mozilla.com

6) Sync milestones and versions between products using syncmsandversions.pl:
   Core -> Core Graveyard (new)
   Core -> MailNews Core (new)
   Firefox -> Toolkit
   Core -> SeaMonkey
   mozilla.org -> Websites (only 1)

7) Move components using movecomponent.pl.
   Any instruction beginning "moved from".
   Can't fix the queries for this - oh well
   <Very long list>
  
8) Rename components using GUI, and fix queries using fixqueries.pl.
   Any instruction beginning "renamed from" or "MailNews: prefix removed".
   <Long list>
  
9) Create new components using GUI.
   Any instruction beginning "new".
   <Long list>

10) Move open bugs using GUI:
    XP Miscellany to Core/General
  
11) Merge components by moving bugs using GUI:
    Any instruction beginning "merge in".
    Merge all bugs, including closed. Delete empty component when done.
    <long list of merges>

12) Close Core Graveyard (and Grendel if necessary) to new bugs

Timing:

- 7) and 8) should be done sequentially, but can be done in either order.
  These are the ones requiring scripts.
  
- 9) and 10) could be done before, after or at the same time.
  These don't require scripts.
  
- 11) could be done any time for those changes which don't also have moves/
  renames as part of them. Otherwise, they need to wait for 7) and 8).

Open questions:
* Firefox/Bookmarks and History - why delay? Can't remember - leave change to 2nd round?
* Password Manager new name - leave change to 2nd round?