Name: EMI EMT-coordination
Start: 2013-04-29T15:00:00+02:00
End: 2013-04-29T16:45:00+02:00
Location: No location set

- 15:00 → 15:10
  
  Welcome
  
  list pf participants
  
  Mandatory & Recommended participants: ALL PTs representatives
- 15:10 → 15:15
  SA2 announcements
  - ..............................
- 15:15 → 15:25
  EMT Action List
  EMI-EMT Action List Tracker
- 15:25 → 15:50
  EMI Releases Status
  Report on status of releases:
  
  EMI-1 (Kebnekaise)
  - EMI 1 Kebnekaise maintenance
  EMI-2 (Matterhorn)
  - EMI 2 Matterhorn maintenance
  EMI-3 (Monte-Bianco)
  - EMI 3 Monte-Bianco maintenance
  - EMI Products Releases tracker
  EMI Components Releases tracker
  
  Important Dates
  Components status:
  - Current Update Cycle - started 01.04 - to be released on 18.04.2013; Planned
    
    EMI 1: -
    EMI 2: 12 products - CREAM GE module, L&B, DPM, LFC, GFAL/lcg_util, ARC CE, Core (Clients, InfoSys, GridFTP server), EMI UI
    EMI 3: 24 products - APEL parsers, publisher, SSM, ARC CE, Core (Clients, InfoSys, GridFTP server), ARGUS, CANl, dCache, DPM, LFC; HYDRA, glite-proxyrenewal, glite-yaim-core, gridsite, L&B, Pseudonymity, STS, UNICORE/X6, UNICORE HILA, VOMS-admin, EMI UI
  Status of testing Globus 5.2.4 Update - missing StoRM
  
  Status of testing XRootd 3.3.1 Update - new update was announced by MattiasE, testing & rebuild of dependent products should start ASAP - ARC & CERN DataMan planned updaes for April cycle
  - EMT report - RfCs status
  - Dashboard - RfCs status
  slides
- 15:50 → 16:00
  EMI Support Status
  Report on EMI support status
  
  GGUS Dashboard - EMI User support Procedure
  
  Support status report - as of 26.04.2013
  - 4 assigned, 0 SLA violations
    CREAM-BLAH - #93438 - LESS URGENT
    DPM Development
    #93453 - LESS URGENT
    #93026 - LESS URGENT
    
    ARGUS - #93508 - LESS URGENT
  Ticket closing campaign - announced by MathildeR
```
Dear EMI product teams,

GGUS still holds 178 open tickets for EMI products (22 of them date back
to 2011, 67 were filed in 2012).
With the release of EMI-3 and its first update release the expectation
is that most of the GGUS tickets currently in an open state are solved
now and can be closed.

Therefore, for each open ticket in the support unit(s) you are
responsible for please proceed as follows:

- in case a solution has been released with EMI-3, _close_ the ticket as
_solved_

- in case a solution will be implemented with the final EMI-3 update
release, _comment_ this in the ticket

- in case a solution will not be implemented at all, _close_ the ticket
as _unsolved_

- in case a solution will be implemented in your product after the end
of EMI, _state_ this in the ticket with a realistic date, when it will
be fixed (ETA)
```
- 16:00 → 16:30
  
  AOB