Changes: design

• Solid, modular design inherited (with some not-so-good bits)
• Lots of refactoring, redesign and clean-up, common in OSS
• Module owners, super reviewers and mozilla.org technical lead have good understanding of design and high-level design changes
• Reasonable amount of design documentation, but hard to keep updated. No UML or structured/visual design docs.
• Code documentation automated on LXR and Unstable.
• Design rationale captured on roadmap, documents, mailing lists, newsgroups
• What is the basic sequence of activities for a change?