| | 64 | * The library has been explicitly posted to be considered a Candidate Boost Library to the following venues: |
| | 65 | * The Boost Users Mailing List |
| | 66 | * The Boost Developers Mailing List |
| | 67 | |
| | 68 | == Processes == |
| | 69 | |
| | 70 | This section describes the processes by which the development of Boost Libraries proceed in a distributed manner. |
| | 71 | |
| | 72 | === Review Process === |
| | 73 | |
| | 74 | There are two types of reviews: |
| | 75 | |
| | 76 | * '''Acceptance Review''' -- the process through which a Candidate Library is reviewed to be accepted. |
| | 77 | * '''Maintenance Review''' -- the process through which all accepted libraries undergo on a regular basis to determine whether it should be deprecated, updated, replaced, or dropped from Boost. |
| | 78 | |
| | 79 | ==== Acceptance Review ==== |
| | 80 | |
| | 81 | The Acceptance Review is driven by at least one Review Manager. The Acceptance Review process goes as follows: |
| | 82 | |
| | 83 | 1. A Candidate Library is identified signalling the beginning of the process. |
| | 84 | 1. A Review Committee for the Candidate Library is convened for the library which consists of: |
| | 85 | * At least one Review Manager. |
| | 86 | * At least one Review Manager Assistant. |
| | 87 | * At least one Trusted Release Manager. |
| | 88 | 1. During the course of the review period, members of the Boost Community answer a set of questions regarding the suitability of a library to be made part of Boost relating to: |
| | 89 | * The design and implementation of the library. |
| | 90 | * The documentation of the library.this is done by Review Managers, Review Manager Assistants, and Trusted Release Managers. |
| | 91 | * The functionality provided by the library. |
| | 92 | * Suitability in real-world application conditions (implies testing on actual platforms, not necessarily in production). |
| | 93 | 1. A conformance test script is run regularly on the library to see whether it satisfies the technical requirements for inclusion in a larger Boost distribution. |
| | 94 | 1. Once a month the members of the Boost Community are surveyed to list down which Candidate Libraries are fit for acceptance into Boost. |
| | 95 | 1. The Candidate Libraries at the top of the list are then checked for whether the issues raised by the community have been addressed appropriately by the Review Committee. |
| | 96 | 1. A Candidate Library is accepted when: |
| | 97 | * The Review Committee agrees that the issues raised by the community have been addressed properly. |
| | 98 | * The conformance test script raises no errors. |
| | 99 | |
| | 100 | Once a library is accepted, the following things happen: |
| | 101 | |
| | 102 | * The Review Managers involved in the process are considered Library Maintainers of the library along with the original Library Maintainers. |
| | 103 | * The Review Manager Assistants involved in the process are considered Contributors to the library. |
| | 104 | * The Review Manager Assistant is then evaluated by the peers in the Review Committee and may be promoted to becoming eligible to be a Review Manager |
| | 105 | * The Release Manager in the Review Committee then pulls the latest tagged release version of the Candidate Library into the distribution she is responsible for |
| | 106 | |
| | 107 | The Acceptance Review process runs until the Candidate Library is accepted. Candidate Libraries may be removed from active review if: |
| | 108 | |
| | 109 | * The project is deemed to be no longer active. |
| | 110 | * There is a request to remove the Candidate Library from active review from the original submitter. |
| | 111 | |
| | 112 | Note: |
| | 113 | |
| | 114 | * There is no time limit to the length of an Acceptance Review. |
| | 115 | * The notes of an Acceptance Review are maintained in a Wiki to be regularly maintained by any member of the Review Committee. |
| | 116 | * Issues raised on Candidate Libraries should be filed as issues in the appropriate issue tracking system associated with the Candidate Library. |
