Release Beta

Integration Activities Description

Official deadline to complete RCB: 30 April

RCB Integration Plan

• one integration build per week (overall 6 integration builds)
• components included in each integration build are those made available on Friday morning at 9h
• last build will include components planned for April 15 and made "Available" in Savane by April 20 at 9h
• components made available after this deadline will be cancelled and not included in RCB
• detailed integration build plan:
  • 1st build: 19 March (components decided on 16/03 morning)
  • 2nd build: 26 March (components decided on 23/03 morning)
  • 3rd build: 02 April (components decided on 30/03 morning)
  • 4th build: 09 April (components decided on 06/04 morning)
  • 5th build: 16 April (components decided on 13/04 morning)
  • 6th build: 20 April (components decided on 20/04 morning)

Making Code Available

• complete the development
• apply your tests
• create an ETICS configuration and associate it with its subsystem configuration
  • configuration should be named: 0_2_x
  • dependencies to other DILIGENT configurations should be defined as "static"
  • dependencies to external configurations should be defined as "dynamic"
  • a correspondent Service Archive configuration should always exist
• change Savane "Status" field to "Done
  • "Release Process" field will be automatically changed to "Available"
• the integration team will check each Friday morning for "Available" components
• the integration team will report on the late components

Build Executions

• one project level daily build of the HEAD components
• one project level daily build of the BETA components
• subsystem builds should be done locally by each partners using the ETICS CLI
  • problem with the installation of ETICS CLI can be send to project-eu-etics-support@cernNOSPAMPLEASE.ch

Deployment Testing Support

• all portlets should provide an installation script to automatically deploy the portlet
  • the script must be included in the portlet Service Archive
  • the script must be described in the portlet Service Profile
  • these tasks should be performed in the same deadline of the portlet

Bug Fixing

• use Savane to be informed about the bugs to fix
  • all bugs will be marked with the release build number where the bug was found
• 2 working days to react to blocker bugs
• 5 working days to react to other bugs
• bug fixing procedure:
  • bug fixing for RCB apply to the HEAD configuration
  • local tests executed by the developer
  • a new CVS tag is created (tag name is up to the developers to decide)
  • the ETICS configuration is updated with the new tag

Certification Conditions

1. all release Alpha certification conditions remain valid
2. components must be packed as a Service Archive
   • automatic generated through Etics
   • stored in DILIGENT repository
   • validated by the Package Repository service
3. components depending on the DL context should integrate the DILIGENT authentication model
   • it must exist a ?service security descriptor? declared in the WSDD
   • it must be integrated with the Delegation Service and Authentication API
4. services must be deployed on a Java WS-Core container
   • deployable through the DL Management
   • HNM must be able to generate a valid RI profile
   • the RI profile must be discoverable through the DIS
5. components must include javadoc documentation
   • automatic generated through a ?Javadoc? Ant target
   • included in the Etics build commands
   • /doc directory must be generated at the root level in the Etics artifact

Documentation

• missing README files have to be provided asap
• documentation should be available in Twiki by April (date to be annouced)

-- PedroAndrade - 13 Dec 2006