Revision as of 13:43, 3 February 2010

Dial In Info:

• please contact for dial in information.

The EclipseLink committers have a regular meeting (currently weekly) to discuss ongoing development issues and projects. All interested parties are welcome to attend. If you have any additional items you wished discussed please add them at the bottom of the agenda including a brief description and any relevant links. Alternatively development issues can be discussed on the EclipseLink Dev mailing list.

* When adding agenda items please send an email to the eclipselink-dev@eclipse.org list notifying attendees. This will ensure attendees are aware of agenda items prior to the meeting.

Call Schedule

The calendar is available in the following formats:
iCal,ATOM News Feed,HTML

Agenda Jan 7, 2010

11 am EST, Thurs Dec 10, 2009

Ad Hoc

• Peter away Thursday Jan 28th
• Need discussion about how the strategy we are using for User Documentation compares to the wiki-based strategy we are using for developer documentation and whether there is merit to changing the way we do developer documentation. This discussion should wait until we have used found all the issues with our User Documentation Strategy.

Release Planning

• 1.1.4: Not yet scheduled - Planned final patch for 1.1.x stream
• 1.2.1: Not yet scheduled
• 2.0.1: Started, Proposed Feb 17th
• 2.1 Helios
  • http://www.eclipse.org/projects/project-plan.php?projectid=rt.eclipselink
• Galileo SR2 - February 26th/2010
  • RC1+0 Jan 18/10: EclipseLink 1.1.x (latest Milestone or Release)

QA

Jan 25-29, 2010:

• Last week
  • Monitor and triaged nightly tests:
    • 1.1.4 - good
    • 2.0.1 - new failures in Foundation (40 tests) - investigating
    • trunk - JBoss tests failed due to build changes - fixed; new DBWS and FL tests failures - investigating
  • Nightly test automation scripts
    • Switching between non-JTA and JTA datasources - 100%
  • Glassfish 3.0 JPA tests - Triaged.
  • WDF (SAP) tests - Ran (without any mod to tests/fwk) OOC against Oracle DB and MySQL. Some test failures encountered, will file bugs today. Can we ask Andreas/Adrian to take a look? Did you have time to run against WLS as focus for next week is EL 2.0.1 testing.
  • Fixed 1 test bug
• This week
  • EL 2.0.1 testing - target 100% functional and 80% certification by end of next week.
  • DB2 9.7 - new
  • Continue with test automation fwk work:
  • WDF - work on these if EL 2.0.1 testing finishes early
  • Fix bugs targeted for 2.0.1
• Backlog
  • Test Infrastructure work
  • Improve stability of DB certification tests

Build

• Milestone Releases
  • 2.1.0 M5 and 2.0.1 M2 (last week)
  • 2.1.0 M5 promoted to Helios M5 integration
  • 1.1.3 Release promoted to Galileo SR2
• Test component build cleanup (Holding)
  • Restructure to allow testing to *not* rebuild product jars (293032)
    • Will use "static targets" as discussed in meeting last week (297217).
    • Tests will not compile when run target called.
      • merged partial work to update standards.
      • migration work for test projects, currently priority 2
  • Need shippable testing artifacts (R2).
• Helios build integration (293034)
  • Need to do p2 consolidation work to manage multiple versions in a single update location.
    • investigation composite repositories
• WDF integration
  • Completed
• jpa.test10 Suite - Holding
  • Explore possibility of using eclipselink.jpa.test from 1.1.3 as a way to certify javax.persistence 1.0 backward compatability in EclipseLink 2.0.x
    • All tests now compiling with trunk, 83% success rate on Test run.
    • Awaiting review by Tom or Peter of test results (still).
  • Need "project name" assuming this gets running 100%

Fixed Bugs:

JPA

2.0.1 - main focus this week

• Bugs - approximately 10 bugs closed
• SQLServer testing clean-up

2.1.0

• Advanced JPA config
  • Fetch groups in progress.
• Advanced JPA Querying
  • wiki started with prioritized feature list (http://wiki.eclipse.org/EclipseLink/Development/2.1/AdvancedJPA_Queries)
• WDF testing

DBWS

DBWS Development

2.0.1

• MTOM attachment support complete
• No remaining bugs open against 2.0.1

2.1.0

• Feature work
  • Scoping out support advanced PL/SQL datatypes (records, collections, mixture of the two) as arguments to Stored Functions
  • Improved Sparse Merge support (an 'Update' operation currently requires the instance to be fully specified in the SOAP message)

SDO / MOXy

2.1.0

• Representation of JAXB Annotations and enhanced MOXy metadata in externalized 'eclipselink-oxm.xml' metadata format Design
• MOXY Dynamic Persistence Design
• JAXB2.2 Compliance
  • JAXB2.2 CQs approved (API, RI, XJC). Need to commit these to Orbit.
  • Also need to submit JAXB2.1.12 jars to Orbit (CQs previously approved for Helios)
• Continued improvements to MOXY marshalling/unmarshalling performance

EclipseLink Incubator

EclipseLink/Development/Incubation

• EclipseLink/Development/Incubator/Extensions
  • FetchPlan incubator active
    • Doug requesting help.
  • Please provide feedback on Proposal for lowering barrier of entry for new database platforms

Bug Status

Bug reports

Foundation and JPA

Open Bugs

Bugs By Target and Priority

Resolved Bugs

Resolved Bugs

New Bugs

Created Bugs

EclipseLink/Development/DevMeetings/ArchiveBugReports