• LarkcProject
• WP5
• ReleasesTimelineMarch2010

Timeline for next prototype releases (Intermediate dates to be completed. Agreed during the Platform Workshop, 31.03-01.04.2010, Stuttgart)

• Alpha 2.0 release + ?SourceForge opening – 09.10.2009

• LarKC Platform Release V1.0 – end March 2010

• LarKC Platform Release V1.1 – end June 2010 (Review Sept 2010) - Major developments ready end May 2010!!!

  • Plug-in API redesign: only RDF types (no Java types) => V2.0? - depending on the consultation results

  • Remote execution - (Evaluation for D5.5.3 before June release)
  • JavaGAT adaptors (Alexey, HLRS)
  • JEE (aka Tomcat) implementation (Reto, Christoph, UIBK)

  • Support for ?MapReduce plug-ins (execution on Hadoop platform) (Spyros, Jacopo, VUA; Matthias, HLRS) - If we need to include performance evaluation, we need it before June! (D5.5.3 end June!)

  • Support to remote execution by Data Layer ("distributed" Data Layer) (Vassil)
  • Implementation of „design pattern(s)“ for each of the remote approaches (see above tasks)

  • Flow Controller (event/error handling, join/split features,...) => Executor (Christoph, Reto) (NO evaluation for D5.5.3 before June release)

    • Detailed timeline to be produced, after WP1 specification (by Reto) is ready -
    • Three major tasks identified:
      • decider / executor split
      • flow split / join
      • data split / join
    • Caching support (Spyros) - (Evaluation for D5.5.3 before June release)
      • Close collaboration with Executor design/development
    • Support for implementation of use cases workflows including:
      • Use of the plug-in annotation language (Luka)

      • Use of context parameter (when needed) => stateless plug-ins (plug-in/workflow developers. Related to Executor development)

      • Pushing functionality into Data Layer (already existing, needs to be used in concrete use cases)
    • Instrumentation, performance assessment, metrics and tests (towards D5.5.3, end June ready for internal assessment) (See work distribution Vassil slides and document ToC). Detailed schedule:
      1. Initial partner draft - you should draft all text below heading 1 and 2 styles + validation section (19/04) - v03
      2. Initial platform testing (03/05) - v04
      3. Platform testing and evaluation (17/05) - v05
      4. Pre-final version of all chapters (31/05) - v06
      5. Finalize all document content (07/06) - v07
      6. Send deliverable for QA (09/06)
      7. Start implementing QA comments (14/06)
      8. Send to Alice (25/06)

• LarKC Platform Release V2.0 – end November 2010 (submission to EC end Dec.)

  • Plug-in API redesign: only RDF types (no Java types)? Depending on consultation result
  • Data Migration („warming-up“) –tbd, collaboration with other WPs (WP4?, WP2?))
  • Monitoring and Instrumentation tools
  • Stress testing
  • Data Layer benchmarking

  • Data Layer Scalability and Distribution => Distributed Data Layer Overlay

  • Implementation of further Design Patterns
  • Refinement of V1.1 release features, bug fixing

• LarKC Platform Release V3.0 (Final Release) – end June 2011 (submission to EC end Sept 2011)

  • Validation of Platform V2.0 and recommendation for the final version – end Feb 2011 (D5.5.4, submission to EC end March 2011)
  • Refinement of V2.0 release features, validation recomm., bug fixing
  • Stress testing
  • Final release including performance report, final architecture, platform manual, …