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"

(Milestones)
(2.0)
Line 48: Line 48:
 
** In progress:
 
** In progress:
 
*** Remaining 40% All the other mappings and methods
 
*** Remaining 40% All the other mappings and methods
*** Target to complete Friday June 26rd
 
 
* 1:1, M:1 Join table
 
* 1:1, M:1 Join table
 
** Code review
 
** Code review
Line 59: Line 58:
 
* Validation API
 
* Validation API
 
** Target - July 13th
 
** Target - July 13th
*** Need to open a CQ and bring in the API into EclipseLink.
 
 
* Cachable
 
* Cachable
 
** Section 3.7.1
 
** Section 3.7.1
Line 65: Line 63:
 
***** Checked in - _tues june 16th_
 
***** Checked in - _tues june 16th_
 
*** Not done - 3.7.2  
 
*** Not done - 3.7.2  
**** Guy on vacation - restarting _Wed June 23rd_
+
* Completed Functionality
** Completed Functionality
+
 
** Filtering Inheritence by type field (Entity Type Expressions)
 
** Filtering Inheritence by type field (Entity Type Expressions)
 
** Association override w Join table
 
** Association override w Join table
 
** CASE
 
** CASE
*** Multi DB testing will be ongoing past this date.
 
 
** JPQL
 
** JPQL
 
** Persistently Ordered Lists
 
** Persistently Ordered Lists

Revision as of 13:49, 8 July 2009


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 June 24 2009

Meeting format:

  • Status
    • 1.1.2 release
    • 2.0 feature status
  • Galileo Checkpoint Status

2PM EST, Wednesday June 24, 2009

Dial In Info: 1-888-967-2253, Conf ID/Password: 486546/486546

Milestones

  • 1.1.3
    • Proposed date - Oct 30th
      • Code freeze Oct 16th
      • monthly milestones starting in August
  • 2.0 - September 29th 2009
    • Release governed by the JPA 2.0 RI development and JavaEE 6.0 schedule

Status updates

2.0

  • Meta Model
    • Complete:
      • first pass Reviewed and checked in thursday May 28th
      • Tests checked in - May 29th
      • Review updates checked in- June 3rd
      • Checked in mapped Superclass patch - June 12th
      • Mapped Superclass Basic Accessor
      • 60% Complete for core mappings and methods
      • Relational descriptor - remove equals
    • In progress:
      • Remaining 40% All the other mappings and methods
  • 1:1, M:1 Join table
    • Code review
    • Check in target friday July 10th
  • Delimited Identifiers
    • Prototyping on the way.
  • Criteria API
    • Testing on going
    • Target Friday 10th july
  • Validation API
    • Target - July 13th
  • Cachable
    • Section 3.7.1
        • implemented and tested
          • Checked in - _tues june 16th_
      • Not done - 3.7.2
  • Completed Functionality
  • DBWS
    • Automated testing - DBWS included in nightly test runs
    • PL/SQL Collection support. Core ORM support & DBWSUtils checked in.
  • SDO
    • EclipseLink1.1.1 fully passes the SDO2.1.1 TCK on JDK1.5 and JDK6.
  • MOXy
    • EclipseLink2.0: targetting JAXB 2.1.x compliancy.

EclipseLink Incubator

wiki site here

  • SDO DAS Update - Checked in SDO DAS
  • Suggestion to put Equinox in Incubator

Bug Status

Bug reports

Foundation and JPA

Open Bugs

Date 1.1.3 1.1.2 1.1.1 2.0 Future/1.1.x Untargetted
July 8, 2009 # 2 0 0 174 323 94
July 8, 2009 0 0 0 136 268 37
June 24, 2009 x 0 0 130 265 37
June 17, 2009 x 0 0 128 263 37
June 10, 2009 x 0 0 123 264 37
June 3, 2009 x 2 0 120 262 37
May 27, 2009 x 2 0 121 256 38
May 20, 2009 x 3 0 117 253 37
May 13, 2009 x 2 1 105 253 40
May 6, 2009 x x 1 104 255 39
April 30, 2009 x x 4 104 163 38
April 22, 2009 x x 3 101 194 40

@ Change due to bug clean-up and removal of enhancements from count. # Changed report to include enhancements.

Bugs By Target and Priority

1.0.x Open -- Note: Needs updating as new targets are added

1.1 Open

1.1x Open

2.0 Open

Untargetted

Resolved Bugs previous week

Date 1.1.2 1.1.1 2.0 Invalid Duplicate Submitted Patch
July 8, 2009 0 0 13 3 1 5
June 24, 2009 0 0 9 2 1 5
June 17, 2009 1 0 2 3 2 1
June 10, 2009 4 0 4 0 0 1
June 3, 2009 7 0 4 2 0 0
May 27, 2009 6 1 3 1 0 0
May 20, 2009 5 2 4 0 1 0
May 13, 2009 x 3 8 1 0 6
May 6, 2009 x 1 10 0 1 2
May 6, 2009 x 1 10 0 1 2
April 30, 2009 x 6 4 1 0 1
April 22, 2009 (2 weeks) x 16 3 7 2 0

Resolved Bugs

New Bugs previous week

Date Targetted 1.1.3 Targetted 1.1.2 Targetted 1.1.1 Targetted 2.0 Future Enhancement Already resolved
July 8, 2009 2 0 0 15 7 12 5
June 24, 2009 x 1 0 2 3 2 1
June 17, 2009 x 0 0 6 2 0 1
June 10, 2009 x 1 0 5 2 2 0
June 3, 2009 x 2 0 3 5 2 4
May 27, 2009 x 0 0 5 4 2 3
May 20, 2009 x 4 0 14 1 1 2
May 13, 2009 x 2 0 5 2 3 3
May 6, 2009 x x 1 6 0 3 5
April 30, 2009 x x 6 4 6 3 7
April 22, 2009 (2 weeks) x x 5 9 8 3 8

Created Bugs

General Issues

  • Running JPA in JavaSE mode on trunk
    • Issues due to jar signing and split javax.persistence package
    • If you run in Java SE with the javax.persistence 1.0.0 jar shipped with EclipseLink and eclipselink.jar you will get security exceptions on our trunk stream (but not our released streams)
    • We solve this in our testing with an unsigned version of the javax.persistence jar. We may have to consider a similar strategy for our "installer-zip" distribution.
  • SPI defaulting
    • We provide a number of service advertisements in META-INF/services of eclipselink.jar
    • It is possible that installing eclipselink.jar to make use of one service (e.g. JPA) will transparently change the provider of another service (e.g. JAXB) to use EclipseLink if the user has not explicitly specified their service providers.
  • Wiki site update
    • Ensure that wiki site reflect state of feature
  • Location of Docs moving forward
    • where to put 2.0 documentation.
    • breaking down features into smaller pages.
    • potential clone of wiki.

Galileo Release Train

Upcoming Issues

The following items require discussion but are not yet at the stage where a solution can be proposed.

Minutes from Past Meetings

References

Back to the top