Difference between revisions of "Role Developer"
From Gcube Wiki
(Created page with '== Role Description == Developers are responsible for the implementation of components (including coding, prototyping, early testing and release to the integration stage). The ma…') |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| 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). | + | * write code for components their are assigned to |
| + | * provide JUnit testsuites for their components | ||
* 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 11: | ||
== 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 here. An updated listing of gCube developers can be found at https://www.openhub.net/p/gCube. |
| + | Every gCube component should include a file named ''MAINTAINERS'' that lists the current developer(s) of the component. | ||
| − | == Procedures | + | == Role Procedures == |
| − | * [[Continuous | + | * [[Continuous Integration procedure|Continuous Integration]] |
| − | * [[ | + | * [[Major/Minor Release Cycle procedure|Major/Minor Release Cycle]] |
| − | * [[ | + | * [[Maintenance Release Cycle procedure|Maintenance Release Cycle]] |
Latest revision as of 18:12, 2 November 2015
Developers are responsible for the implementation of components (including coding, prototyping, early testing and release to the integration stage). Their main tasks are:
- write code for components their are assigned to
- provide JUnit testsuites for their components
- 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 here. An updated listing of gCube developers can be found at https://www.openhub.net/p/gCube.
Every gCube component should include a file named MAINTAINERS that lists the current developer(s) of the component.
