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

Difference between revisions of "EclipseLink/Development/DevMeetings"

m (→‎MOXy / SDO)
(→‎Release Planning)
Line 30: Line 30:
  
 
== Release Planning ==
 
== Release Planning ==
−
* 2.3.2 - GA Early December
+
* 2.3.3 - GA ??
−
** RC1 - Nov 25
+
** M1  - Jan 11
 +
** M2  -  
 
* 2.4.0 - GA early Mar  
 
* 2.4.0 - GA early Mar  
 
** M7  - Nov 23 (Nov 30 - done)
 
** M7  - Nov 23 (Nov 30 - done)

Revision as of 12:07, 12 January 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.gifiCal,Xml.gifATOM News Feed,Html.gifHTML



Agenda Oct 13, 2011

11 am EST, Thurs


Ad Hoc

Release Planning

  • 2.3.3 - GA ??
    • M1 - Jan 11
    • M2 -
  • 2.4.0 - GA early Mar
    • M7 - Nov 23 (Nov 30 - done)
    • M8 - Dec 7
    • M9 - Dec 21
  • Indigo SR2 - GA Feb 24, 2012
    • RC1+0 - Jan 16 (2.3.3 ?)
    • 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 (backed-out M5)
    • M4+1 - Dec 12
    • M5+1 - Jan 30

Migration to Git

  • Kick off meeting scheduled
    • Will discuss identified issues, and collect additional.
  • Git demo (later)
  • Transition targeted after we branch for 2.4
    • infrastructure and transition plan need to be completed well before.

QA

Dec 29 2011 - Jan 5, 2012:

  • EclipseLink Nightly Results (Updated on 2012-01-05)
    • trunk - 1 new failure with jpa-spring testing - developer is working on it; 5 new failures with jpa on JBoss testing - investigating; DBWS examples failed on all application servers, due to dependency change - developer is still investigating. (the last results is 2012-01-05)
    • 2.3.2 - SDO server-testing failed on WAS 8 - not specific for 2.3.2, dev only fixed in trunk, need to be decided by management if or when the fix will be backported to 2.3 stream. (the last build is 2012-01-04)
    • 2.2.2 - no new build (the last build is 2011-09-28)
    • 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
    • Investigate test failures in Spring - in progress
    • Sybase - 14 new failures - investigating
  • Test Dev
    • JAX-RS: ported JAX-RS tests to MAIN, encountering issues, investigating
  • Test infrastructure
    • Migrated automated server tests to OEL5 linux box -- previous OEL6 box unstable
  • This week:
    • Review 2.4 features; planning for 2.4 certification testing
    • Investigate JPA failures on JBoss (all versions)
    • Investigate performance/OOM issues in JAXB tests
    • infra enhancement: Migrate configuration files to the central location for better maintenance
    • Schedule JAX-RS tests into nightly runs

Build

Jan 5, 2012:

  • Milestone Releases
    • 2.4.0 M8 - Dec 9
    • 2.4.0 M9 - Dec 23
    • 2.4.0 M10 - Dec 29
    • Next: Jan 11 (2.4.0 M11)
  • API scanner - need to review (hold til Doug returns)
  • add Hermes test bundle to build/ship? - working on plan
  • Tycho (New Build)
    • Fixed builder dependencies, which blocked DBWS features from installing from P2
    • Re-integrate DBWS Builder and tests.
      • Currently still using Ant
      • Tycho re-adoption delayed until oracleddl can be made available via P2 (can proceed, but current solution is a hack)
      • OracleDDL now buildable, working on deployment model
  • Git
    • Issues page started at: http://wiki.eclipse.org/EclipseLink/Build/Git
    • Updates ongoing
    • Initial meeting held
    • Had discussions with Webmaster, preliminary Git repo available - has issues.
      • Way too big (45min to clone - offsite)
      • Had some import issues.

JPA

  • 2.4
    • Schema provisioning
    • MT - enhancements
    • MT - Table per tenant

DBWS

DBWS Development DBWS Roadmap

2.4

  • Feature: Parse DDL to extract database metadata
    • DDL Parser now available through Maven repository
    • Reviewed priorities for 2.4 release
      • 362002 - DBWSBuilder should generate CREATE and DROP DDL for 'shadow' JDBC types
      • 325124 - DBWS should support weakly-typed package REF CURSOR
      • 339721 - DBWS should support strongly-typed package REF CURSOR
      • 363535 - DBWSBuilder should set javaClassName for Object/Varray/ObjectTable types to NOT be in Java's default package
      • 329435 - DBWS does not handle %ROWTYPE mix of PL/SQL types and JDBC Advanced types=
      • 339909 - DBWS should support optional argument queries
    • DBWS server tests: Need to review these and ensure they are checked into SVN

MOXy / SDO

RoadMap

2.4

  • Some issues with EE6 CTS tests need to be resolved with EclipseLink 2.4
    • Looks to be related to latest JDK7 version - issues also seen with webservice testing framework
  • MOXy performance issues when running SpecJ2010 benchmark
  • 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 tests: Need to ensure default EclipseLink JAXB used in WLS (no need to set jaxb.properties)
    • Need SDO server tests running in GF3.1.x

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

Retrieved from "https://wiki.eclipse.org/index.php?title=EclipseLink/Development/DevMeetings&oldid=284454"

Back to the top