Difference between revisions of "EclipseLink/Development/DevMeetings"

From Eclipsepedia

Jump to: navigation, search
(QA)
(QA)
Line 77: Line 77:
 
Jan 3-10 , 2013:  
 
Jan 3-10 , 2013:  
  
* EclipseLink Nightly Results (Updated on 2012-12-20)
+
* EclipseLink Nightly Results (Updated on 2013-01-10)
** master - 21 new failures with wdf testing on javaSE and all application servers - investigating; one new failure with jpa-lrg on h2 DB - investigating; both foundation and jpa testing on TimesTen-11 - related to DB configuration, will be investigated by QA; jpa test-lrg failed on all application servers - related to the changes with classpath in order to support jpa21, investigating; server-test-custom-features failed on WAS - investigating. (the last build is 2012-12-20)
+
** master - several new failures with jpa on derby-10 testing - developer is working on it; several new failures with jpa2.0 testing on jpa2.1 - seems to be intermittent, will manually re-run to verify; 1 new test case for DBWS test-service failed on all application servers - investigating; jpars testing didn't run properly (hangup) on WLS 12.1.1 - investigating; . (the last build is 2013-01-10)
** 2.4.2 -  both foundation and jpa testing on TimesTen-11 - same as master. (the last build is 2012-12-19)
+
** 2.4.2 - 3 new failures with jaxb testing \-investigating; jpars testing didn't run properly (hangup) on WLS 12.1.1 - same as master. (the last build is 2013-01-09)
 
** 2.3.4 - no new build (the last build is 2012-11-25)
 
** 2.3.4 - no new build (the last build is 2012-11-25)
 
* Testing
 
* Testing

Revision as of 11:55, 10 January 2013



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 Nov 29, 2012

11 am EST, Thurs


Ad Hoc

No Call Dec 27th

Release Planning

  • 2.3.4 - GA January
    • M1 - pending
  • 2.4.2 - GA TBD
    • M3 - Dec 6 (Complete)
    • M4 - Jan 9 ** SR2 Build **
    • M5 - Feb 6
  • 2.5.0 - GA Mid 2013 (from M4 on - Milestones 3rd Wednesday of Month)
    • M5 - Nov 21 (Complete)
    • M6 - Jan 10 (was Dec 19)
    • M7 - Jan 30 (was Jan 16)
    • M8 - Feb 20 (back on 3rd Wed schedule)
    • M9 - Mar 20
    • M10 - Apr 17
  • Juno SR2 - Feb 22 (Milestone dates are when contibution is due)
    • RC1+1 - Jan 14
    • RC2+1 - Jan 28 (Orbit will be ready and "R")
    • RC3+1 - Feb 4
    • RC4+1 - Feb 11
  • Kepler - June 2013 (Milestone dates are when contibution is due)
    • M3+1 - Nov 12 (2.5.0 M4)
    • M4+1 - Dec 17 (2.5.0 M4&M5)
    • M5+1 - Feb 4
    • M6+1 - Mar 18

Build

RoadMap

Dec 13, 2012:

  • Milestone Releases
    • none
  • EclipseLink to Maven Central
    • Applied for hosting via Sonatype OSS Forge
      • accepted. Working on seting up hosted repos
  • JPA 21 testing
    • JPA Test needs to be refactored (convoluted configurations, build xml 92 pages long)
    • JPA21 mostly functional. Ongoing refactoring proceeding.
  • Issues targeted for investigation post JPA21 test working.
    • Select Bundle not working with OpenJDK
    • JPA-RS testing not running at Eclipse
  • Update Git Repo descriptions
  • Fix ASM corruption on our Maven Repo

QA

Jan 3-10 , 2013:

  • EclipseLink Nightly Results (Updated on 2013-01-10)
    • master - several new failures with jpa on derby-10 testing - developer is working on it; several new failures with jpa2.0 testing on jpa2.1 - seems to be intermittent, will manually re-run to verify; 1 new test case for DBWS test-service failed on all application servers - investigating; jpars testing didn't run properly (hangup) on WLS 12.1.1 - investigating; . (the last build is 2013-01-10)
    • 2.4.2 - 3 new failures with jaxb testing \-investigating; jpars testing didn't run properly (hangup) on WLS 12.1.1 - same as master. (the last build is 2013-01-09)
    • 2.3.4 - no new build (the last build is 2012-11-25)
  • Testing
    • Manually ran jpa2.1 tests on javaSE (added these tests in jpa-lrg) -- investigate 4 tests failures on Oracle DB (but passed on MySQL DB) -- 397611
    • Helped reproduce hanging issues with JPA-RS on WLS 12.1.1
  • Test Dev
    • JPA 2.1 tests running on GF - changes to allow both JPA 2.0 and JPA 2.1 tests to run
  • Test infrastructure
    • Added jpa-lrg (jpa2.0 and jpa2.1 tests) running against jpa2.1 persistence API in nightly testing
  • This week:
    • Investigate several failures with JPA 2.0 tests running against JPA 2.1 persistence
    • jpa2.1 sessionbean & advanced model on GlassFish to verify server test framework changes
    • Fix DBWS server test failures
    • JPA tests cleanup

JPA

  • JPA 2.1 work progress.
    • DDL generation
    • Treat
  • JPA-RS
    • JPA-RS: Respect "Accept" header for SingleResultQuery
    • JPA-RS: XMLMarshalException when executing a named query (XML) assigned
    • JPA-RS: NPE when executing a named query (JSON)

MOXy / SDO

RoadMap

2.4.2

  • Performance
    • JAXB context initialization and annotation processing during application deployment

2.5.0

DBWS

DBWS Development DBWS Roadmap

2.5

  • Conversion from native metadata

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

Bug Status

Bug reports

Foundation and JPA

Bugs By Target and Priority

Resolved Bugs

Created Bugs


EclipseLink/Development/DevMeetings/ArchiveBugReports