This change will require adding Linux, at least, to the Netscape 6 commercial tinderbox group, but it should liberate most of the current SeaMonkey machines to be used for the trunk. The new mozilla.org build lab machines can make up any difference. They will remain within bugzilla's database as long as old bugs refer to them, of course. There will still be a Future target milestone. To tell whether the bug is likely to be fixed by that milestone, anyone can check the Target Milestone setting in the bug.
Developers target milestones as usual.
Mozilla also needs project management, not just community effort in adding target milestone keywords to bugs, and distributed developer initiative in targeting new milestones appropriately. See below under the project management heading for more. The following table shows the new milestone schedule with very rough dates. We may well slip every one of these milestones somewhat, but we're aiming at quarterly milestones. It's important that Mozilla developers, especially contributors planning to release commercial products based on Mozilla code, be able to count on regular milestones.