John Wiegand and Erich Gamma made a keynote speech in Eclipsecon 2005 entitled Eclipse Mode: Processes that Adapt, explaining why the development process of eclipse was so successful.
Milestone (Milestones-i) is a cycle every 6 weeks. Each milestone in the city is a small development cycle (mini dev cycle). Plan/execute/test/review. The milestone development reduces the pressure.
Continuous integration (continuous integration) fully Automated system construction and testing. The daily nightly construct discovers the integration issues between the different components. Weekly integration constructs and all automated unit tests must be executed successfully (at least when we are using them ourselves). The construction of the milestone provides a good enough system for the entire eclipse community to use.
Always beta (Always Beta) every construction is considered a candidate release, and we expect it to work. The component team uses the latest code every day, the project team uses the integrated, and the community uses the milestone-constructed system.
The previous development of collective participation (Community involvement) is not to publish the source code, but also rarely communicate. A transparent development process is now required. The whole community needs to know how and how to participate. Need to develop participatory and enhance the value of Community contribution
Question: No one knows what new features are addressed in the next milestone: releasing new and Noteworthy features (noteworthy)
Continuous testing (continuous testing) did not initially have unit tests, which was like driving with blindfolded eyes. There are now more than 20,000 JUnit test units that are closely linked to the entire build process. Only when all the tests are green (in JUnit, Green indicates that the test passes), the inheritance constructs pass. We have 3 different kinds of tests: correctness, performance, resources
End Game (endgame) prior to the official release or a summary process (convergence processes). Includes a series of tests-corrective processes. Each time such a process increases costs. Focus on high priority issues. There are no full-time testers here.
Problem: Very tiring Process solution: Allocate to every release, not focus on milestones
Final Closure, in the name of the Elcipse Project team, publishes "Eclipse x.x now available"
Relax yourself (decompression) The recovery period after each release. Be free to explore new things, review the last cycle (the task, the failure, the process, the communication between the groups). Start planning the next release process.
Time of each cycle
Release cycle: 12-16 months milestone: 9 months end game: 1-2 months relaxation period: 1 months
Here is the first part. Refer to Eclipsepowered.org
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.
