Difference between revisions of "Software Integration and Distribution: Overview"
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| + | |||
| + | This section is meant to document the procedures and tools used for the gCube System releases. | ||
| + | |||
| + | |||
| + | Given the big size of the gCube system, its highly modularity and the high number of developers involved in the implementation, the Work Package 7, responsible for the distribution of gCube, defined a set of procedures that formalize and make it easy integrate, test, document and distribute the software by coordinating the different persons involved in the release process. Section [[Release Procedures]] provides a detailed description of each procedure by listing for each procedure' step who do what. | ||
| + | |||
| + | |||
| + | Activities in release procedures are highly automated and supported by several tools. The tools offers support in the i) configuration of gCube source code ([[SCM tools]]), ii) in the release preparation phase ([[Trac]]), iii) in the software integration phase ([[ETICS]], [[BTRT]], the [[Building Infrastructure]]), iv) in the testing phase ([[Static Code Analysis|Checkstyle]], [[Static Code Analysis|Findbugs]], [[ETICS]], the [[Testing Infrastructure]]), v) in the documentation ([[gCube System documentation wiki|Wikimedia]]) and vi) Distribution ([[gCube Web Site and Distribution Site|gCube Distribution Site]]). | ||
| + | |||
| + | |||
| + | Section [[Testing Plan]] provides documentation for the support to gCube software testing carried out during integration of system's releases and in continuous integration builds. | ||
Revision as of 13:11, 16 January 2012
This section is meant to document the procedures and tools used for the gCube System releases.
Given the big size of the gCube system, its highly modularity and the high number of developers involved in the implementation, the Work Package 7, responsible for the distribution of gCube, defined a set of procedures that formalize and make it easy integrate, test, document and distribute the software by coordinating the different persons involved in the release process. Section Release Procedures provides a detailed description of each procedure by listing for each procedure' step who do what.
Activities in release procedures are highly automated and supported by several tools. The tools offers support in the i) configuration of gCube source code (SCM tools), ii) in the release preparation phase (Trac), iii) in the software integration phase (ETICS, BTRT, the Building Infrastructure), iv) in the testing phase (Checkstyle, Findbugs, ETICS, the Testing Infrastructure), v) in the documentation (Wikimedia) and vi) Distribution (gCube Distribution Site).
Section Testing Plan provides documentation for the support to gCube software testing carried out during integration of system's releases and in continuous integration builds.
Release Roles
Release Tools
- SCM Tools
- Building tools
- Tracking System - Trac
- Testing Infrastructure
- Documentation
- Distribution Site
Release Procedures
- Continuous Integration
- Major/Minor Release Cycle
- Maintenance Release Cycle
- Documentation Writing guidelines
- Documentation Validation procedure
- Distribution procedure
Test Plan
