John Wiegand and Erich Gamma have a topic speech entitled "Eclipses: Processes That Adapt" in EclipseCon 2005, which explains why eclipse's development process is so successful.
Milestones first is one cycle every 6 weeks. MINI DEV CYCLE. Plan / Execute / Test / Review. Milestone development has reduced pressure.
Continuous integration (Continuous Integration) fully automated system constructors. Daily evening constructs will find integration problems between different components. Weekly integrated constructs and all automated unit tests must be successfully performed (at least enough to be in our own use). Milestone constructs, provide the entire Eclipse community to use a sufficiently good system.
Always beta (always beta) each construct is considered a candidate Release, we look forward to it. The component team uses the latest code daily, and the project group uses the integrated, and the community uses a milestone constructed system.
The development of community involvement is not published in the source code, and it is very little to communicate. Now you need a transparent development process. The entire community needs to know how to participate, how to participate. Need development-based participation, improve the value of community contributions
Question: No one knows what new features in the next milestone: Release new and worthless features (New and Noteworthy)
Continuous Testing initially has no unit test, which seems to be blinded. Now, more than 20,000 JUnit test units are closely linked to the entire building process. Only when all the tests are green (JUnit, green means testing), inheriting constructs can pass. We have three different tests: correctness, performance, resources
EndGame is officially released or there is a summary process (CONVERGENCE Process). Includes a series of tests - corrected processes. Every time this process increases costs. Focus on the problem of high priority. There is no full-time tester here.
Question: Fatigue process resolution: Distributed to every release, not before the milestone
Final Closure releases "Eclipse X.x Now Available" with the name of the elCIPSE Project Team
Relax yourself (Decompression) Restoration period after Release. You can explore some new things freely, review the last cycle (reached the task, failed place, process, and communication between the group). Start planning the next release process.
Each cycle time
Release cycle: 12-16 month milestones: 9 months end game: 1 to 2 months to relax: 1 month
Here is the first part. See eclipsepowered.org for details
