Difference between revisions of "EclipseLink/Development/DevMeetings"

Revision as of 12:10, 31 October 2007

Developer Meetings

Agenda Oct 31st 2007

Status updates

- M1
  - Status on putting TopLink changes into EclipseLink - Peter K
  - Build and Installer Status - Tom W
  - Download, wiki, www - Doug C
  - Status on OXM, JAXB, SDO - Dave M
  - Documentation Status Update - Rick S.
  - Sign off on packaging/zip name - Doug

- Update on Testing Status - Chris D and Mike N

General Issues

- Ottawa Demo Camp [1] - Doug
- Current Dev Process - Tom
  - Code submission email template (before and after M1) - Mike O'Brien
  - Min Requirements
  - Bugzilla
  - Specs
- Common build.properties procedure for running both inside/outside eclipse - proposed by mobrien
- code coverage in eclipse (IE: EclEmma) - Mike O'Brien
- Goals M2 - Doug and Peter
- Where to put Workbench - Doug
  - Utils Component

Agenda Oct 17th 2007

Purpose: Discuss Testing strategy for EclipseLink tests.

• ChrisD, MikeN - what we've done so far ...

Minutes

• brief discussion of strategy
• short-run goal: understand scope of testing requirements with view to reduce number of frameworks
• long-run goal: propose consolidated test framework plus migration of existing tests

• Action Items

• MikeN, ChrisD - put together a 'straw-man' proposal for consolidated test framework based on current understanding of testing requirements

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. ?

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.

• Publish testing status
  • Testing on Open Source DB
    • MySQL
• Document usecases that are expected to work
  • JPA
  • MOXy (Native OXM - JAXB, SDO postponed to future sprint)
  • 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
  • Requirements for automated testing
• 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
• Story for Derby - what tests are expected to pass

• 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