Changes between Version 15 and Version 16 of DevProcess
- Timestamp:
- Aug 22, 2015, 10:53:44 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevProcess
v15 v16 1 1 = The BOINC development process = 2 3 = BOINC software development overview =4 2 5 3 BOINC is free software, distributed under the [http://www.gnu.org/copyleft/lesser.html Lesser General Public License] … … 11 9 who may then use the code for any purpose that it desires. 12 10 13 * [DevProcess The BOINC development process]14 * [DevProjects Help wanted - programming]15 11 * [DevQualityAssurance Quality Assurance Workflow] (under discussion) 16 * [TranslateIntro Help wanted - translation]17 12 * [//email_lists.php boinc_dev], an email list for BOINC developers 18 13 * [CodingStyle Coding style] 19 14 * [DebugClientWin Debugging the client on Windows] 20 15 21 BOINC development is done by BOINC staff, by the staff of various BOINC-based projects, and by volunteer programmers. Development is divided into several areas. Each area is managed by an 'owner'. 16 Development is divided into several areas. 17 Each area is managed by an 'owner'. 22 18 23 19 || '''Area''' || '''Owner''' || '''Key contributors''' || 24 || API || David Anderson || Bruce Allen, Bernd Machenschalk||20 || API || David Anderson || || 25 21 || BOINC Manager || Rom Walton || Charlie Fenton || 26 || Client || David Anderson || John !McLeod, Carl Christensen||22 || Client || David Anderson || || 27 23 || Mac OS X || Charlie Fenton || || 28 24 || Testing and release management || Rom Walton || || 29 25 || Server || David Anderson || Kevin Reed || 30 26 || Translations of GUI and web text || Rom Walton || || 31 || Unix build system || Reinhard Prix || Eric Korpela||27 || Unix build system || Eric Korpela || || 32 28 || Web features || David Anderson || Rytis Slatkevicius, Janus Kristensen || 33 29 || Windows installer and screensaver || Rom Walton || || 34 30 35 31 36 The BOINC development, testing and release process is shown below. Ovals represent people, rectangles represent information channels. A, B, C, D and E represent the different BOINC development areas. 'Owner A' represents the person who owns area A, as shown above. 37 38 [[Image(//dev_flow.png)]] 32 The BOINC development process involves interaction between various groups: 39 33 40 34 == Participants == 41 35 42 * Report bugs (or learn of workarounds)on the BOINC message boards.43 * Learn of new releases on the BOINC web site.44 * Note: we need ways of 'pushing' info to participants, e.g. via the Manager.36 * Report bugs on the BOINC message boards. 37 * These are reported by message board moderators to the relevant area owner. 38 * Participants may also file bug reports in Github. 45 39 46 40 == Area owners == 47 41 48 * Reads the relevant BOINC message board on a regular basis. Decides if new bugs are present. Adds entries to the BOINC/Trac bug database. 49 * Monitors the relevant categories of the BOINC/Trac bug database. Manages entries (delete, merge, prioritize, assign). 50 51 == Developers == 52 53 * Are assigned tasks via BOINC/Trac. 42 * Fix bugs or delegate to contributors. 54 43 55 44 == Alpha testers == 56 45 57 * The [//email_lists.php boinc_alpha email list] is used to give instructions, and for discussion of tests and procedures. 58 * If bugs are found, log them in BOINC/Trac. 59 * Use web-based interface for submitting test summaries. 46 * Test development releases and report problems via a Web-based system. 60 47 61 48 == Release manager == 62 49 50 * Monitor the Alpha-test results and notify area owners of issues. 63 51 * Decide when to create test releases; communicate with alpha testers via [//email_lists.php email list]. 64 * Decide when to make public releases , based on web-based reports and on contents of BOINC/Trac.52 * Decide when to make public releases.
