Release Beta Meeting CERN, 1-2 March 2007 ACTIONS

1. Release Beta MeetingCERN, 1-2 March 2007ACTIONS Roberta Faggian Marque

2. Actions - Build • First integration build, March 12 • New integration build will be defined every week including the new components made “Available” (0_2_X) • ACTION: Developers to make available their ETICS configuration for components/subsystem and modify status in Savane to Done so that the component will become Available - ENG to draft • Inclusion of new components up to April 15, the one made available afterward will be cancelled • ACTION: integration team to notify the TCom about the components that cannot be included in RB because of late schedule (after April 15) - CERN to draft • Bug fixing in all activities will consider the prioritisation given by the analysis of the dependencies • ACTION: Lino to update the analysis on RB components and distribute priorities • Configuration will be frozen once for RCB and once for final version of RB (after bug fixing) Wrap-up session

3. Actions - Build • De-coupling/Parallelisation of the activities: • Build will be executed every day automatically (archive repository maintained in in the Report Browser: grid16) • Latest version copied in grid17 for deployment testing • Testing will be able to get the artifacts they need from grid16 looking at the reports for deploytest • on-demand subsystem build will be possible • Heads builds: • Automatic night-builds • Discourage on-demand subsystem builds • Requirement to ETICS: the system should allow to disable guest access to Package Repository and Report Browser • ACTION: ENG will collect the requirements for ETICS (CERN to provide input) set up discussion with ETICS and get an answer on how these can be addressed Wrap-up session

4. Actions - Deployment Test • Portlets will be manually tested (no automatic deployment possible). Deployment script will have to be provided by the developers (included in the Service Archive) • ACTION: CERN to set tasks for developers • Deploytest will use DL Management and Package Repository (these will be tested manually) • ACTION: CERN to send requirements/bugs to CNR • System deployment testing • Few selected configurations for the system deployment could be tested for deployment on a best effort base • Deployment Testing infrastructure • Should be independent from testing activity at least until RCB • ACTION: ENG will make machines available to CERN • ACTION: CERN to send ETICS requirements for deployment testing to ENG Wrap-up session

5. Actions - Testing • Major issues: • Testing infrastructure configuration • artifacts will be downloaded from grid16 • ACTION: 4DSoft could spend 2 days at CERN to learn about deployment on the week 19-23 March • After RCB sharing between Deployment Testing and Testing activity could be re-discussed (Support for sub-VO can be exploited) • Availability of an initial test case for each service • ACTION: 4DSoft will send a request for few examples of what they need, selected teams will have to implement it. Consequent decision if same approach can be applied to others • Developers support through Savane • Blocker bugs: 2 working days • Other bugs: 5 working days • Release: build number • ACTION:communicate this decisions at the next Tcom Wrap-up session

6. Actions - Certification • Agreement on certification conditions (in addition to RA conditions) • ACTION: Lino to send e-mail informing the partners about agreed certifications conditions (circulate draft to integration team) • Step1: Service Archive must exist • ACTION: CERN to implement in deployment testing • Step2: authentication integration • ACTION: CNR to verify if HNM is able to check these conditions at deployment time • Step3: deployment on Java WS Core Container • ACTION: CERN to cover this on deployment testing activity • Step4: inclusion of Javadoc documentation • ACTION: UoA to perform the manual checking on two predefined deadlines (beginning and end of April) Wrap-up session

7. Actions - Documentation • Documentation (in wiki) final deadline is end of April • ACTION: UoA to set up intermediate deadlines with partners (April 16) • README files • ACTION: UoA will re-new the request for missing files Wrap-up session

8. Actions - General • ACTION: ENG to organise weekly integration phone meeting on Friday at 11h, first one will be Friday, March 9. New components ready, late components and support tasks will be listed, progresses from all activities will be presented. • ACTION: Lino to raise licensing issue for decision for RB • ACTION: Lino to set up the next TCom where these decisions will be communicated • ACTION: re-discuss branches usage. Proposal: new developments branch can be created after RCB. RB will continue on heads up to the release. After, heads will merge the new developments for final and a new branch will be used for bug fixing in RB. Wrap-up session

9. Original Work Plan Prepare validation infrastr. ARTE IMPECT validation RB Certification RF Certification RF integration and testing support RA testing support RB integration and testing support RB bug fixing RF bug fixing RF bug fixing Minimal bug fixing RB bug fixing RA Testing RCB Testing RCF Testing RB Testing RF Testing post-RA integrations RCB integration RB integrations RCF integration RF integrations RB new developments RF new developments Feb Mar Apr May Jun Jul Aug Sep Oct Nov RB RCF RF RA RCB RB plan RF plan Wrap-up session

10. RB BUILD repository week1 0.2.2 week2 weekX 0.2.1 BUILD1 BUILD1 GRID 17 BUILD2 BUILD2 BUILD3 BUILD3 BUILD4 BUILD4 BUILD5 BUILD5 BUILD6 BUILD6 BUILD7 BUILD7 Additional on-demand sub-system builds 0.2.x BUILD1 BUILD2 BUILD3 BUILD4 BUILD5 BUILD6 BUILD7 GRID16 LATEST correctly build Deployment Test Testing Wrap-up session