EMI EMT Action List

#	Date	Summary	Who	Due Date	Status	Comments
1	-	Service Reference Cards	PTs	-	In progress	2010-09-08 (CA) SRC done by ARC-CE, link provided by APEL, ARGUS 2010 -09-09 (CA) updates from dCache, DGAS 2010-10-17 (CA) updated SRC Links
2	-	PTs participants	PTs	10/09/2010		2010-09-08 (CA) - updated EMTMeetingsParticipants; replies from ARC, UNICORE, 7 gLite PTs; missing: dCache, StoRM, DGAS, gLite InfoSyst, AMGA, EMI Registry, EMI Messaging 2010--09-09 (CA) replies from dCache, StoRM 2010-09-10 (CA) updated EMTMeetingsParticipants
3	-	EMI releases code-names	everybody	-		2010-11-29 PEB: EMI 0 - Zugspitze (Germany), EMI 1 - Kebnekaise (Sweden), EMI 2 - Matterhorn (Switzerland), EMI 3 - Monte Bianco (Italy/France)
4	-	ETICS-configuration responsible contact	PTs	10/09/2010		2010-09-10 updated ETICS-configuration responsible table
5	-	List of dependencies	PTs	10/09/2010	In progress	2010-09-10 updated PTDependenciesList
6	-	JAVA version in EMI	PTs	2010-10-18		2010-10-15 (CA) dCache & StoRM still have to test OpenJDK 2010-12-09 - dCache server now uses SunJDK by temporarily setting the JAVA_HOME
7	-	glite-info-generic/templates mainteners	Pedro Andrade	2010-11-02	In progress	2010-10-29 Maria Alandes Pradillo - obsolete packages (link to ResourceBDII)

During the first EMT meeting 5 task-forces were created: Software Integration, Software Packaging, Software QA, Software Release Process

Software Integration & Configuration

tries to find the right answers to:

• What level of integration is required among middleware distributions?
• Is it required to uniformly configure the software? How?
• How to configure software for integration, packaging, testing and development? Does it have to be the same system?
• What tools to be used?
• How to manage 3rd-party libraries?
• How to manage dependencies among distributions?
• Is it required to setup development environments? How?

People involved: Lorenzo Dini (ETICS, GL), Anders Waananen (ARC), Mattias Ellert (ARC), Björn Hagemeier (UNICORE). Bernd Shuller (UNICORE), Owen Synge (dCache), Francesco Giacomini (gLite), Eamonn Kenny (gLite), Cristina Aiftimei (EMI), Pedro Andrade (gLite)

WIKI: Task-Force Integration & Configuration Guidelines: Configuration and Integration

Software Packaging

tries to find the right answers to:

• What level of conformance to Fedora and Debian guidelines?
• Are EMI-specific conventions required (Versioning scheme, naming, extra constraints)?
• What packaging tools?
• How to package uniformly for Fedora and Debian?
• Do the integration and packaging tools have to be a single system?
• How often to release packages to distributions? How?

People involved: Lorenzo Dini (ETICS, GL), Anders Waananen (ARC), Mattias Ellert (ARC), Andre Giesler (UNICORE), Owen Synge (dCache), Francesco Giacomini (gLite), Eamonn Kenny (gLite), Cristina Aiftimei (EMI), Björn Hagemeier (UNICORE). Bernd Shuller (UNICORE)

WIKI: Task-Force Packaging & Releasing Guidelines: Packaging

Change Management & Release Process

tries to find the right answers to:

• How to handle changes in software?
• Are gLite Patches suitable?
• What is the release workflow?
• How to attach bugs to releases?
• How to manage YUM/APT repositories?
• What platforms to support?
• What tools to track changes, bugs, releases?
• Bug categories, states, other fields, etc.

People involved: Maria Alandes Pradillo (gLite, GL), Francesco Giacomini (gLite), Pedro Andrade (gLite), Bernd Schuller (UNICORE), Björn Hagemeier (UNICORE), Anders Waananen (ARC), Owen Synge (dCache), Antje Petersen (dCache), Cristina Aiftimei (EMI)

Guidelines:

• Change Management Guidelines
• Releasing

Software QA - Metrics Generation Guidelines

tries to find the right answers to:

• What Metrics? Software, process, language specific?
• How to define thresholds?
• Is an integrated testing environment required? How?
• How to generate metrics? Automatically or Manually?
• Who generates metrics?
• How to uniformly extract metrics from Bug Trackers?
• What format to use to communicate, store and display metrics?
• What level of continuous integration? Are Nightly builds/tests OK? Test on commit?
• What tools?

People involved: Eamonn Kenny (gLite, GL), Jozef Cernak (ARC), Giuseppe Fiameni (UNICORE), Gianni Pucciani (gLite), Andres Abad Rodrigues (ETICS), Lorenzo Dini (ETICS), Andrea Ceccanti (gLite), Owen Synge (dCache), Antje Petersen (dCache).

Guidelines: Metrics Generation

Software QA - Certification & Testing Guidelines

tries to find the right answers to:

• general testing guidelines: which kind of tests to perform and when,
• how to write a Software Verification and Validation Plan,
• how to perform certification on a release candidate,
• how to write a Software Verification and Validation Report.

People involved: Jozef Cernak (ARC, GL), Gianni Pucciani (gLite), Michele Carpene (UNICORE), Owen Synge (dCache)

WIKI: Task-Force: Certification & Testing

Service Reference Cards:

All PTs should provide this summary information for the services they develop, following the template SRCTemplate

-- DoinaCristinaAiftimiei - 06-Aug-2010