Engineering Management Team (EMT): is lead by the Release Manager and composed of the Product Team Leaders (or duly appointed representatives), a QA representative, a Security representative, representatives of the Operations teams of the major infrastructures (EGI, PRACE, etc.) and invited experts as necessary. The role of the EMT is to manage the release process and the 'standard‘ changes, that is all the changes that are pre-approved based on established policies and do not need to be individually approved by the PEB or the PTB. This includes software defects triaging and prioritization, technical management of releases, integration issues, and user support request analysis. The EMT is therefore the natural aggregation point for all PTs to discuss practical integration and release issues and is adapted to the largely distributed nature of the project. This mechanism has been already successfully employed in other very distributed projects like EGEE III. The Release Manager reports to the SA1 Work package leader.

EMT Useful Links

• Indico Agendas: http://indico.cern.ch/categoryDisplay.py?categId=3077
• Minutes: EMTWeeklyMeetings
• Actions List short link: http://bit.ly/emi-emt
• Mailing List Archive: http://mail.eu-emi.eu/mailman/private/emt/
• Members/meeting participants: EMTMeetingsParticipants
• Contacts: * EMI Product Teams *

EMI Release Management

• EMI Releases Performance
• EMI Release Management
  • EMI Updates Schedule Methodology
  • EMI package signing procedure
  • EMI Beta & Acceptance Testing
  • EMI Release Preview Testbed
  • EMI 0 Activity
  • EMI 1 Activity - activity done in order to release the first EMI release (Kebnekaise)
    • EMI 1 Updates - activity done to support and maintain the EMI 1 (Kebnekaise) release
      • Porting EMI 1 to SL6/x86_64
    • EMI 1 NBs results - page used to collect old NB reports, for up-to-date situation see link above.
  • EMI 2 Activity - activity in progress in order to release the second EMI release (Matterhorn)
    • EMi 2 Updates - activity done to support and maintain the EMI 3 (Matterhorn) release
  • EMI 3 Activity - activity in progress in order to release the third EMI release (Monte Bianco)
    • EMI 3 Major & INcompatible Changes and Ugrade paths
    • EMI 3 Updates - activity done to support and maintain the EMI 3 (Monte Bianco) release

• Common problems and suggested solutions
• EMT discussions/decisions
• EMI presence in upstream distributions/repositories
• Managing Globus Updates in EPEL
• Managing XROOTD Updates in EPEL
• EMI Documentation problems and comments

EMT metrics reports

Bug Listing Dashboard

Weekly reports:

EPEL compliance report

EMI User Support

• EMI User Support:
  • EMI UserSupport-HowTo
  • GGUS Assigned tickets reports:
    • Tickets_Assigned_15_07_2011.xls: GGUS tickets Assigned, 15.07.2011
    • Tickets_Assigned_22_07_2011.xlsx: GGUS tickets Assigned, 22.07.2011

EMI Generic Documentation:

• Generic Installation & Configuration for EMI 1
• Generic Installation & Configuration for EMI 2
• Generic Installation & Configuration for EMI 3
• UI
• WN
• EMI Nagios
• CREAM LSF module
• CREAM Torque module
• TORQUE server config
• TORQUE WN config
• Service Reference Cards: SRC Template & SRC Links
• EMI Services Documentation: EMIServicesDocs

Task forces:

• YAIM in EMI
• Major Release version in EMI

• "old" EMTActionList twiki

-- DoinaCristinaAiftimiei - 06-Aug-2010