Difference between revisions of "EclipseLink/Development/DevMeetings"

Revision as of 15:26, 3 October 2007

Developer Meetings

Agenda - Oct 03 2007

Purpose: discuss milestones for Eclipse Persistence Services 1.0M1

• Automated Build
• Automated Test
• Testing on Open Source DB (Derby or MySQL)
• Document usecases that are expected to work
• about.html
• Initial component reorganization
  • DBWS
  • MOXy
  • SDO
  • EIS
• Small set of manual server tests
• Regular CTS run within Oracle
• IP Log accurate
• Build dependancies checked in (CDDL source files we depend upon

compiled to jars)

• Document "works with Oracle"
• How To Get Started Docs
  • JPA
  • MOXy
  • SDO
  • EIS
• Document how to build
• Document how to test
• Document requirements for check-in
• Remove deprecated packages and classes. ?

Proposed Agenda Oct 10th 2007

Purpose: Testing strategy and layout for EclipseLink tests. Issues include:

• automated scripts
• ease of debugging failing tests
• which databasees?

Minutes

• Moving toward a 1.0 Release
• Timebox M1 vs making it feature rich
• Milestones should match 4 week sprint.
  • Sprint Goal - 1.0M1 release
• First milestone is Nov 5th.

• Document usecases that are expected to work
  • JPA
  • MOXy
  • Native ORM

• Supporting migration from TopLink 10.1.3, 11g
  • Package renamer on client source
  • Investigate reading in 10.1.3, 11g metadata
• Full Testing story
  • Published testing status
  • Requirements for automated testing
  • Testing on Open Source DB
    • MySQL
    • Story for Derby - what tests are expected to pass
• Automated Build
  • Having all the jar files checked in
  • Oracle Strategy to check in classfiles that reference Oracle Classes
  • Build.xml
  • get a cron job run on the EclipseServer
• Consumer Focused Collateral
• about.html

• Action Items
  • Managers: number of available resources - deadline Oct 4th
    • Managers and Dev team: Build task list
  • Dev team: break above into tasks - deadline Oct 4th
  • SprintPlanning Meeting: Friday Oct 5th

• Initial component reorganization
  • DBWS
  • MOXy
  • SDO
  • EIS

- Automated Test - Small set of manual server tests - Regular CTS run within Oracle - IP Log accurate - Build dependancies checked in (CDDL source files we depend upon compiled to jars) - Document "works with Oracle" - How To Get Started Docs

   * JPA
   * MOXy
   * SDO
   * EIS

- Document how to build - Document how to test - Document requirements for check-in - Remove deprecated packages and classes. ?