Difference between revisions of "Role Release Manager"

From Gcube Wiki
Jump to: navigation, search
Line 8: Line 8:
 
* grant rights in the scope of the project (e.g. to [[Role Subsystem Manager|Subsystem Managers]])
 
* grant rights in the scope of the project (e.g. to [[Role Subsystem Manager|Subsystem Managers]])
 
* receives notifications from [[Role Subsystem Manager|Subsystem Managers]] about new Subsystem releases
 
* receives notifications from [[Role Subsystem Manager|Subsystem Managers]] about new Subsystem releases
 +
  
 
== Role Assignment ==
 
== Role Assignment ==
Line 17: Line 18:
 
|}
 
|}
  
== Role 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 16:25, 25 September 2015

Role Description

The Release Manager is responsible for the management of the gCube Release and Maintenance Cycles. The main tasks are:

  • publishes the release plan with deadlines for opening/closing the releases
  • manages daily build scheduling and executions
  • monitors defects and activities at project-level
  • creates new Subsystems in ETICS
  • creates project configurations aggregating Subsystem configurations
  • grant rights in the scope of the project (e.g. to Subsystem Managers)
  • receives notifications from Subsystem Managers about new Subsystem releases


Role Assignment

Release Manager Partner
Gabriele Giammatteo (Maria Antonietta Di Girolamo) ENG


Role Procedures