Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

EclipseLink/Development/DevMeetings

< EclipseLink‎ | Development
Revision as of 10:54, 27 October 2011 by Eric.gwin.oracle.com (Talk | contribs) (Release Planning)



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 Oct 13, 2011

11 am EST, Thurs


Ad Hoc

Release Planning

  • 2.3.1 - GA late Oct
    • RC1 - Oct 17 (Complete)
  • 2.4.0 - GA early Mar
    • M5 - Oct 26 (In progress)
    • M6 - Nov 9
    • M7 - Nov 23
    • M8 - Dec 7
  • Indigo SR2 - GA Feb 24, 2012
    • RC1+0 - Jan 16
    • RC2+0 - Jan 30
    • RC3+0 - Feb 8
    • RC4+0 - Feb 13
  • Juno - GA Jun 2012
    • M1+1 - Missed
    • M2+1 - Sept 26 (2.4.0-M3) (Complete)
    • M3+1 - Nov 7 (2.4.0 M5?)

Migration to Git

  • Kick off meeting to be scheduled
    • Git demo?
  • after we branch for 2.4

QA

October 20-27, 2011:

  • EclipseLink Nightly Results (Updated on 2011-10-27)
    • trunk - 6 new failures with core-lrg - dev is investigating; 16 new failures with oracle extension testing, they are all related to change using xdb6.jar instead of xdb .jar - Bug filed against Oracle JDBC; 1 new failure with jaxb, seems to be related to the change with xmlparserv2.jar - investigating; server-test-composite failed on all WLS servers (10.3.5 with and without patch) - investigating; 12 new failures with jpa-server-test on Glassfish v3.1.1 - investigating; 6 new failures with foundation lrg on jdk1.7, same tests failed on h2 DB as well - investigating;  3 new failures with custom features on WAS - investigating; DBWS examples failed on Glassfish (both v3.1.2 and 3.1.1) - investigating. (the last results is 2011-10-27)
    • 2.3.1 - 2 new failures with jaxb on jdk1.7 - investigating; 16 new failures with oracle extension testing, and 3 new failures with custom features on WAS - same as trunk, they are all related to use xdb6.jar, QA is investigating them; SDO server-testing failed on WAS 8 (both AS and ND) - server configuration issue, passed on WAS 7, low priority. On hold. (the last build is 2011-10-26)
    • 2.2.2 - no new build (the last build is 2011-08-03)
    • 2.1.4 - no new build (the last build is 2011-09-27)
    • 2.0.3 - no new build (the last build is 2010-11-25)
    • 1.2.1 - some failures with jpa testing on both JavaSE and JaveEE, they are all related to the environment setting, e.g. $JAVA_HOME or $JROCKIT_HOME. QA need to update the testing environment setting if there is a new release or new check it with this branch. (the last build is 2011-09-30)
  • Testing
    • 2.3.1 closedown - complete, will continue to monitor nightly results
    • Oracle 11.2.0.3 issues - resolved (fwk still pointing to 11.2.0.2 jars)
    • Doc review
  • Test Dev
    • JAX-RS integration with EclipseLink JAXB - 98%
      • Manual testing of this scenario passed with Glassfish and WebLogic SErver
      • Automation Glassfish: resolved deployment issue -- tests are now running but has Assert error - investigating
      • Automation WLS: Assert error as well
  • Test infrastructure
    • Migrated EclipseLink Nightly Testing to use the new report with tabbed navigation - 80%
  • This week:
    • JAX-RS integration with EclipseLink JAXB
    • Doc review EL 2.3
    • JAX-WS test project scoping
    • Resolve issues with SDO / WAS 8
    • (backlog) Change EclipseLink Nightly Testing scripts for Tycho adoption in trunk - continue to monitor what else needs to be done
    • (backlog) Migrate to new EclipseLink Nightly Testing report using tabs
    • (backlog) Add "is.JPA1.0" flag in WDF server testing framework in order to skip those JPA2.0 tests on only JPA1.0 supported application servers.

Build

October 13, 2011:

  • Milestone Releases
    • 2.4.0 M5 (Oct 27 - 2.4.0.v20111026-r10274) (in Progress)
    • Next: Nov 9 (2.4.0 M6?)
  • API scanner - need to review (hold til Doug returns)
  • add Hermes test bundle to build/ship? - need to review
  • Tycho (New Build)
    • Completed.
  • Git
  • Troubleshooting Maven uploads

JPA

Oct 13

  • Bug fixes in 2.3.1
  • 2.4
    • Schema provisioning
    • MT - enhancements
    • MT - Table per tenant

DBWS

DBWS Development DBWS Roadmap

2.4

  • Feature: Parse DDL to extract database metadata
    • This is a change in the way we access type metadata, that will cover off the following enhancement requests
      • 325124 DBWSProvider does not handle package REF CURSOR
      • 339721 DBWS should support strongly-typed package REF CURSOR
      • 339909 - DBWS should support optional argument queries
      • 329435 - DBWS does not handle %ROWTYPE mix of PL/SQL types and JDBC Advanced types
    • CQ 5483 (JavaCC v5.0) - PMC approved
    • Sprints
      • Sprints 4&5 complete: PL/SQL Record, Collection Types, including nested support
      • Sprints 6&7: Advanced Oracle types, PL/SQL types using %ROWTYPE% and %TYPE% macros
    • Eclipse-hosted GIT repository
      • Runtime code will be folded back into SVN once parity with 2.3.1 functionality is mostly complete
      • Writing up a proposal for leaving the standalone DDL Parser in GIT, and just providing the jar in SVN. This would save migrating everything back to SVN for potentially just one release.
  • RESTful DBWS (DB-RS)
    • Capturing requirements in a wiki for review

MOXy / SDO

RoadMap

2.3.2

  • Bug fixing - some MOXy performance issues highlighted

2.4

  • Object model mapping to JSON
  • MOXy footprint reduction
    • Investigating how MOXy's dependency on foundation can be simplified to reduce binary/jar footprint
  • Feature extensions
    • Set of JAXB feature extensions targetted for 2.4 capture on roadmap (link above)
  • Server integration testing
    • JAX-RS testing: Working with QA to set up JAX-RS tests running in WLS & GlassFish

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

Bug Status

Bug reports

Foundation and JPA

Bugs By Target and Priority

Resolved Bugs

Created Bugs


EclipseLink/Development/DevMeetings/ArchiveBugReports

Back to the top