Difference between revisions of "Role Developer"
From Gcube Wiki
Luca.frosini (Talk | contribs) (→Procedures Involvement) |
|||
| Line 1: | Line 1: | ||
| − | + | Developers are responsible for the implementation of components (including coding, prototyping, early testing and release to the integration stage). Their main tasks are: | |
| − | Developers are responsible for the implementation of components (including coding, prototyping, early testing and release to the integration stage). | + | |
* run local/remote component builds | * run local/remote component builds | ||
* check that component dependencies are compliant with settled requirements | * check that component dependencies are compliant with settled requirements | ||
| Line 10: | Line 9: | ||
== Role Assignment == | == Role Assignment == | ||
| − | Since the high number of people playing this role and role's dynamism, it is too much complex to keep a list of all gCube | + | Since the high number of people playing this role and role's dynamism, it is too much complex to keep a list of all gCube developers. Every gCube component should include a file called "MAINTAINERS" that lists the current developer(s) of the component. |
| − | == Procedures | + | == Role Procedures == |
* [[Continuous Integration procedure|Continuous Integration]] | * [[Continuous Integration procedure|Continuous Integration]] | ||
* [[Major/Minor Release Cycle procedure|Major/Minor Release Cycle]] | * [[Major/Minor Release Cycle procedure|Major/Minor Release Cycle]] | ||
* [[Maintenance Release Cycle procedure|Maintenance Release Cycle]] | * [[Maintenance Release Cycle procedure|Maintenance Release Cycle]] | ||
Revision as of 14:53, 28 September 2015
Developers are responsible for the implementation of components (including coding, prototyping, early testing and release to the integration stage). Their main tasks are:
- run local/remote component builds
- check that component dependencies are compliant with settled requirements
- accept/fix defects in component
- interact with VCS
- create/edit component configurations
- notify Subsystem Manager about component releases
Role Assignment
Since the high number of people playing this role and role's dynamism, it is too much complex to keep a list of all gCube developers. Every gCube component should include a file called "MAINTAINERS" that lists the current developer(s) of the component.
