Description
Objectives: identify list of tasks to be done, processes to be in place, documents to be released before project launch in April 2004.
Attempt to identify possible events that could impact significantly JRA1.
Identify people to be assigned in various working groups (QA, Security, EMT, Architecture) and their tasks.
Identify meetings, their participation, frequency and location.
Identify list of issues.
-
Alberto Aimar28/10/2003, 14:00Alberto will describe the tools and processes in place for SPI (LCG Software Process Infrastructure)
The idea is then to keep this in mind in the next two sessions to see what issues would be raised when adopting the SPI approach. Go to contribution page -
Erwin Laure28/10/2003, 14:30Items to be discussed: LCG-2 support, Middleware hardening, Common software organization, VDT/Globus, Containers, Unit Testing, Software Engineering Tools, People assignments. What will be part of the first release, who is going to be responsible.Go to contribution page
-
Maite Baroso28/10/2003, 15:05Items to be discussed: Tools, Nightly builds, Nightly Tests, Testing process and validation rules (document needed).
Site1/Site 2 tests. Which are the site, who is taking responsibility, what is the timing (PM3?)
CVS, autobuild, autoinstall, testing, testbed needed (i.e. Integration testbeds presumably inherited from EDG; who will commit?) Go to contribution page -
All28/10/2003, 15:40Items to be discussed: this is mainly about processes.
Which (documented processes) are needed. For example we need strict rules on interface definitions and freeze, as well as a process to make them change.
How do you go from Release Candidate to manufacturing. Who are the members, how often do we need to meet. Go to contribution page -
All28/10/2003, 16:00