Revision as of 12:14, 6 June 2012

Dial In Info:

• please contact Peter Krogh 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 Apr 19, 2012

11 am EST, Thurs

Ad Hoc

Review of 2.4 Dev page:

 http://wiki.eclipse.org/EclipseLink/Development/2.4.0

Please ensure that this page has tasks that are scheduled for 2.4.

Release Planning

• 2.3.3 - GA June - July
  • M1 - Jan 11 (Complete)
  • M2 - May 10 (Complete)
  • M3 - Jun 07
• 2.4.0 - GA June 15
  • M15 - Mar 8 (Complete)
  • M16 - Mar 19 (Complete)
  • M17 - Apr 3 (Complete)
  • M18 - Apr 18 (Published 26th)
  • M19 - May 6 (Complete)
  • M19.1 - May 9 (Complete)
  • M20 - May 16 (Pending reorg)
  • M21? - May 23
  • Branch from Trunk - At M20/21 (pending reorg)
  • Showstopper codefreeze - B.O.D. May 28
  • RC1 - E.O.D. May 28
• 2.4.1 - (2.4 Branch update) June 15 (Post Juno RC4)
  • Git Hands-on - mid-June
  • Git Migration - July
• Juno - GA Jun 2012 (Dates are when contibution is due)
  • M1+1 - Missed
  • M2+1 - Sept 26 (2.4.0-M3) (Complete)
  • M3+1 - Nov 7 (backed-out M5)
  • M4+1 - Dec 12 (2.4.0-M8) (Complete)
  • M5+1 - Jan 30 (2.4.0-M12)(Complete)
  • M6+1 - Mar 19 (2.4.0-M16)(Complete)
  • M7+1 - May 7 (2.4.0-M19)(Complete)
  • RC1+1 - May 21 (M20)
  • RC2+1 - May 28 (RC1)
  • RC3+1 - June 4
  • RC4+1 - June 11

Migration to Git

• Dev process FAQ
  • http://wiki.eclipse.org/EclipseLink/Development/Process/Git
• Git demo (later)
  • TBA
  • Tortiose Git is available for Windows (Beta)
    • Team transition may now be seemless (except for mavenization)
      • when using putty should use "git.eclipse.org" as profile name
    • Full test repo is available for testing at:
      • ssh://git.eclipse.org/gitroot/eclipselink/org.eclipse.eclipselink.test.git
• Transition targeted for early July
  • Maven build/directory migration to follow
  • infrastructure and transition plan in the works.
    • Am translating build for Git use (change in qualifiers)
    • Once prototype build complete and have migration tooling configured:
      • will proceed with migration
      • will overlay modified build.
      • hope to keep downtime to a few days.
• Status
  • SVN to Git translation having trouble properly rooting branches
    • means transactions are there, but state at branch is not
    • tried several tools.
    • am looking at 'rebuilding' repository rather than migrating
      • migrate to branch point, branch, migrate to next, branch...,then importing branch transactions from an existing import

QA

May 24-31, 2012:

• EclipseLink Nightly Results (Updated on 2012-05-31)
  • trunk - 1 new failure with oracle extension testing - investigating; 2 new failures with test-oracle-aq - investigating; lots of failures with jpa static weaving testing - investigating; all wdf testing failed - investigating be developer; jaxb and oxm on jdk16 didn't run properly - investigating. (the last build is 2012-05-31)
  • 2.4.0 - 18 new failures with foundation lrg and 10 new failures with oracle extension testing - developer had checked in the fix, need to wait for the new build to verify; 2 new failures with test-oracle-aq - investigating; lots of failures with jpa static weaving testing - investigating (looks like intermittent, but need to verify); jaxb with woodstox3 parser testing didn't finish on jdk16 - investigating; both WAS-nd 7 and 8 didn't run properly - investigating (seems to be related to the testing environment, all tests worked fine on both WAS-as 7 and 8). (the last build is 2012-05-30)
  • 2.3.3 - several new failures with jpa2.0 TCK - investigating (seems to be related to the issue with database). (the last build is 2012-05-30)
• Triage
• Testing
  • 2.4 Release Testing -- in progress
    • completed JPA configs testing - for WLS 10.3.6, WLS 12.1.1, GF 4, and WAS 8
    • Remaining: Postgre, Sybase, cache co-ordination
  • Investigated and fixed JAXRS failures on WebLogic -- new org.eclipse.persistence.jaxb.rs.MOXyJsonProvider
• Test Dev
  • JPA-RS tests running on servers
    • found several issues (GF 3.1.2) which were fixed by dev
    • all tests pass on GF 3.1.2 with new fixes
    • Working on automation scripts
• Test infrastructure
  • Test and infrastructure changes to adopt NoSQL/EIS reorganization
• This week:
  • EclipseLink 2.4 release testing
  • Add JBoss 7 to nightly testing - requires some test fwk changes
  • JPA-RS
  • Setup performance tests 2.4.0 vs. 2.3.0
• Backlog:
  • Investigating Enable JPA 1.0 TCK on GlassFish v3
  • Review table-per-tenant functionality
  • Add Open JDK certification tests
  • Upgrade to WAS 8.0.0.3
  • Git migration
  • Enable JPA 1.0 TCK on GlassFish v3
  • 370988 - JAX-RS tests need to be separate project in order to avoid dependency issues in Eclipse IDE
  • oracle specific tests failures on GlassFish - tried suggestions from dev, but not successful - on hold
  • optimize setup/teardown of JAXB junit testcases

Build

May 17, 2012:

• Milestone Releases
  • M20 holding
  • Next: M20
• API scanner - need to review (hold til Doug returns)
• Remove old build pathways
  • mostly complete.
  • working on converting Oracle build to Tycho
• release prep...
  • Nosql reorg. finalizing build/process/packaging changes

JPA

• 2.4
  • Schema provisioning
    • Checked in Early Feb
  • RCM support for refreshMetadata
    • Checked in Jan 20th
  • Metadata caching
    • Slipped out of 2.4
  • JPA-RS
    • EclipseLink/Development/2.4.0/JPA-RS/REST-API
    • REST API updates

MOXy / SDO

RoadMap

2.4 features

• JSON Design Doc
• JAXB RI extension support

2.4.1

• Performance
  • Focussing on SpecJ benchmark runs
• Jar footprint reduction

• QA, Testing
  • Bug 374765 - EclipseLink 2.3 SDO server test failed on GlassFish

DBWS

DBWS Development DBWS Roadmap

2.4

• Feature: Parse DDL to extract database metadata
• Final support for REF CURSOR packages checked in - following bugs resolved
  • 339721 - DBWS should support strongly-typed package REF CURSOR - support for simple JDBC IN args
    • Complex JDBC argument support: 379029 - DBWS: Need support for PL/SQL and advanced JDBC args in a stored proc/func with a ref cursor out/return arg

EclipseLink Incubator

EclipseLink/Development/Incubation

• Time to create separate sub-project for incubator
  • Increase community of committers
  • Try out GIT & eGit/jGit tooling in incubator?

Documentation

Preparing for 2.4 items. Ben put the EL doc plan on the wiki at http://wiki.eclipse.org/EclipseLink/Development/Documentation/2.4

Considering process improvements

JPA Doc: http://wiki.eclipse.org/EclipseLink/UserGuide/JPA

MOXy/JAXB Doc: http://wiki.eclipse.org/EclipseLink/UserGuide/MOXy

DBWS Doc: http://wiki.eclipse.org/EclipseLink/UserGuide/DBWS

Bug Status

Bug reports

Foundation and JPA

Bugs By Target and Priority

Resolved Bugs

Created Bugs

EclipseLink/Development/DevMeetings/ArchiveBugReports