EclipseLink/Development/DevMeetings

From Eclipsepedia

Jump to: navigation, search



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.gifiCal,Xml.gifATOM News Feed,Html.gifHTML



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 - Apr 20
  • 2.4.0 - GA June 15
    • M15 - Mar 8 (Complete)
    • M16 - Mar 19 (Complete)
    • M17 - Apr 3 (Complete)
    • M18 - Apr 18
    • M19 - May 2
    • Branch from Trunk - At M19
    • M20 - May 16
    • 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 (M19)
    • RC1+1 - May 21 (M20)
    • RC2+1 - May 28 (RC1)
    • RC3+1 - June 4
    • RC4+1 - June 11

Migration to Git

  • Dev process FAQ
  • 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

April 12 - 19, 2012:

  • EclipseLink Nightly Results (Updated on 2012-04-19)
    • trunk - 1 new failure with Oracle-Specific testing - test case issue, and developer is working on it; several jpa testing (in DDLGenerationExtendTablesJUnitTestSuite) failures on all application servers except WAS - investigating by QA. (the last build is 2012-04-19)
    • 2.3.3 - 1 new failure with test-oxm on xmlparserv2.jar - investigating. (the last build is 2012-04-17)
  • Triage
    • NestedUnitOfWorkReadOnlyClassTest in Oracle-Specific test suite failed at reset stage - Vikram Bhatia is investigating
  • Testing
    • wdf testing failed on JBoss server with deployment issue in EL2.4, bug: 376773
  • Test Dev
    • JAX-RS / JSON - in progress - 70%
    • Cache Co-ordination tests on WebLogic Clusters - 0%
  • Test infrastructure
    • Test infra refactoring work in progress -- centralizing all test infra files in one location for easier management; eliminates out of sync files when updates are made
  • This week:
    • JPA-RS functionality - review code and tests checked in by dev; run tests on server
    • JAX-RS / JSON
  • Backlog:
    • oracle specific tests failures on GlassFish - tried suggestions from dev, but not successful - on hold
    • Git migration
    • JPA server tests against MongoDB
    • 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
    • optimize setup/teardown of JAXB junit testcases

Build

April 19, 2012:

  • Milestone Releases
    • Next: M18
  • API scanner - need to review (hold til Doug returns)
  • add Hermes test bundle to build/ship
    • done
  • Add JPA-RS
    • incorporating into nightly build and installer packaging
  • incorporate javax.persistence, asm, antlr, sdo, hermes as transitive deps in Maven repo.
    • Avoids users needing to specify multiple versions to use maven with eclipselink or bundles.

JPA

  • 2.4
    • Schema provisioning
      • Checked in Early Feb
    • RCM support for refreshMetadata
      • Checked in Jan 20th
    • JPA 2.1
      • initial checkin: Stored procedure support
      • initial checkin: SQL result set mapping - new constructor support.
    • Metadata caching
      • Prototyping underway
    • JPA-RS

MOXy / SDO

RoadMap

2.4

  • Bugs
  • JSON support
    • JSON Design Doc
    • External metadata file now supported in JSON as well as XML
    • Discussion with GF team on configuring Jersey to use EclipseLink JSON binding.
  • JAXB RI extension support
    • EE6 CTS tests seen on JDK1.7.0
  • QA, Testing
    • MOXy dependency issue with newer Tycho version, could be resolved by moving to JDK6
    • 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
    • DDL Parser now available through Maven repository
      • 339721 - DBWS should support strongly-typed package REF CURSOR
    • Testing
      • Bug 373380 - The DBWS examples failed to deploy on GlassFish3.1.2
      • Reviewing Web Service test plan for completeness
      • Reviewing IDE test scenarios

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