JRA1 meeting - assessing the EMI 2 status of the product teams

Name: JRA1 meeting - assessing the EMI 2 status of the product teams
Start: 2011-12-12T10:00:00+01:00
End: 2011-12-12T12:00:00+01:00
Location: EVO

Monday 12 Dec 2011, 10:00 → 12:00 Europe/Zurich

EVO

Hide

Emergency JRA1 telcon meeting, 12/12/11 10:00-11:45

PTs present:

AMGA - no-one present
APEL - John Gordon excused
ARC CE - David Cameron
ARC Client - Martin Skou
ARC Container - Aleksandr Konstantinov couldn't connect to EVO, no problematic/no-response tasks
ARC GridFTP server - Aleksandr Konstantinov couldn't connect to EVO, no problematic/no-response tasks
ARC infosys - no-one, no problematic/no-response tasks
ARGUS - Andrea Ceccanti, Mischa Sallé, Oscar Kooero
gLite infosys - Laurence Fields
gLite compute - Massimo Sgaravatto, Marco Cecchi
dCache - Patrick Fuhrmann
gLite sec - John White, Mischa Sallé, Oscar Kooero
DGAS - Andrea Guarise
CERN data - Oliver Keeble
CESNET Security - Zdenek Sustr
gLite MPI - no-one present, no problematic/no-response tasks
L&B - Zdenek Sustr
SAGA - Laurence Fields
StoRM - Richardo Zappi
Unicore Client - Björn Hagemeier
Unicore Services - Bernd Schuller
Unicore Container - Bernd Schuller
Unicore Security - Bernd Schuller
VOMS - Andrea Ceccanti
Messaging - Lionel Cons
EMI COLIN - Zdenek Sustr

EMIR - Shiraz Memon, Ivan Marton

1) EMI 2 deadlines and code handover to SA1

There is a dedicated EMI 2 wiki page[1]. The page contains the deadlines of release candidates and other details about EMI 2. This page will be updated and should be checked repeatedly. The first deadline is the code freeze for Wednesday. No development should be continued after that day. However, life is not always that easy. That's why we need to check status of the tasks now, and see what can be finished and if we need to extend deadlines for some of the late tasks.

Handover: When development is finished and put in VCS, development task should be set to done, and the work will move over to the release tracker.

If a development task is delayed and has low priority PEB may require you to drop the work on that task and move over to higher priority tasks.

Certification and testing in release tracker should be charged on JRA1, not SA1.

If you want to release some dev task which is, e.g. 80% done, make a comment in the dev task stating that this is done and for which version/release the task is partially released.

2) Individual product team reports on their "problematic" and "non-responsive" dev tasks

Went through all PT tasks with status "problematic" and "no response":

Problematic and non-responsive high-level objectives will be discussed on PTB level tomorrow.

Next step is that PTB will go through the late, problematic tasks and set new code freezes for the delayed tasks tomorrow.

3) aob

EVO is a pain

[1] https://twiki.cern.ch/twiki/bin/view/EMI/EMI-2

There are minutes attached to this event. Show them.

The agenda of this meeting is empty