When Berkeley release a new version of BOINC, World Community Grid do not adopt it immediately. Instead, new releases undergo a thorough vetting process: 1.
* The World Community Grid staff wait to see whether the release is stable in widespread distribution on other BOINC projects. Most releases fail at this step. Generally, it takes some months before a release reaches a stable version. 2.
* IBM security auditing and review. At this stage, a number of issues will be identified that need addressing, as well as new features that World Community Grid require for the release to be acceptable. 3.
* World Community Grid technicians work with the Berkeley developers to implement and test the required changes. 4.
* Internal testing begins. The Community Advisors are the first b
| Attributes | Values |
|---|
| rdfs:label
| |
| rdfs:comment
| - When Berkeley release a new version of BOINC, World Community Grid do not adopt it immediately. Instead, new releases undergo a thorough vetting process: 1.
* The World Community Grid staff wait to see whether the release is stable in widespread distribution on other BOINC projects. Most releases fail at this step. Generally, it takes some months before a release reaches a stable version. 2.
* IBM security auditing and review. At this stage, a number of issues will be identified that need addressing, as well as new features that World Community Grid require for the release to be acceptable. 3.
* World Community Grid technicians work with the Berkeley developers to implement and test the required changes. 4.
* Internal testing begins. The Community Advisors are the first b
|
| dcterms:subject
| |
| abstract
| - When Berkeley release a new version of BOINC, World Community Grid do not adopt it immediately. Instead, new releases undergo a thorough vetting process: 1.
* The World Community Grid staff wait to see whether the release is stable in widespread distribution on other BOINC projects. Most releases fail at this step. Generally, it takes some months before a release reaches a stable version. 2.
* IBM security auditing and review. At this stage, a number of issues will be identified that need addressing, as well as new features that World Community Grid require for the release to be acceptable. 3.
* World Community Grid technicians work with the Berkeley developers to implement and test the required changes. 4.
* Internal testing begins. The Community Advisors are the first beta testers beyond the staff and developers. More issues are identified at this stage. 5.
* Once all the major issues are resolved, a public beta test is announced, usually via the Beta Test Announcements forum. 6.
* The final version is promoted to the World Community Grid recommended version, and replaces the previous version on the download page. The new version is announced in the Member News forum. 7.
* Berkeley integrate the fixes contributed by World Community Grid into their own client, and they release a new recommended version.
|
![[RDF Data]](/fct/images/sw-rdf-blue.png)