1. Software Release Procedure Session MANAGEMENT and FUTURE directions Form ongoing ‘empowered’ Technical Discussion Group (TDG) Any future project definitions(resources etc.)should follow a design TDG should review project with a view to reducing complexity and resolving outstanding issues SECURITY Need a documented procedure for integrating new CANeed definition ins Need security APIs for each WP INFORMATION SYSTEMS Define functionality required for resource discovery, matching,monitoring in an implementation independent way VO MANAGEMENT.Need definition in terms of quotas, priorities etc.

2. TESTING organisation Strengthen Test Group and define its management and integration in project Define Test Suites for all phases and group responsibilities Test Suites to be distributed with software Clarify use of Bugzilla for tracking features TESTING PROCEDURES Do nightly rebuild with ‘head’ rather than last ‘tagged’ version Perform daily static analysis with an automated tool Each WP must provide ‘configuration’ tests Full application testing to come last in multi-stage procedure RESOURCES for TESTING etc.. Clarify support for ‘external’ s/w e.g Globus,Condor-G (?LCG) Clarify integration of EDG/LCG resources for test/validation SCOPE of RELEASE MANAGER ? Relation to managemnt (see J Templon proposal) Must have flexibility in people’s roles. Priorities defined by management. NEW DOCUMENT New version in one week. Inputs to Z Sekera

3. Atlas Task Force work ‘Long Job’ problem Clearly document procedures for data management Decouple application s/w installation Make Atlas RPMs relocatable General Software Issues Build in tracing and logging to s/w development. To make debugging feasible Fully document all compatibility issues with new versions

4. PROJECT MANAGEMENT ORGANISATION and RELEASE MANAGER Tech manage group. authorise feature mods. determine development priorities Release manager. consult with middleware, determine release, inform management. request new tests. define Beta test period. organise release distribution (including docs and CDs). enforce release date. authorise critical fixs to beta release User Supprt Manager. determine new ctivities fro user support group. make sure all bugs get into bugzilla Project Management + all project members. bring s/w to high quality

5. Quality Group Gabriel Zaquine Actions: –Monitor final test plans –Review of existing QA documements –Provide a document with proposals to improve quality inside WPs Open discussion points: –Static metrics –Bugzilla pending anomalies follow up –How to control, validate, facilitate interaction and interfaces between WPs –How to provide quality culture inside the project