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"

(→‎Foundation and JPA)
(→‎1.1.0)
Line 44: Line 44:
 
*** Started
 
*** Started
 
* [http://wiki.eclipse.org/EclipseLink/Development/DBWS DBWS]
 
* [http://wiki.eclipse.org/EclipseLink/Development/DBWS DBWS]
−
** First release of the Database Web Service (DBWS) component
 
 
** Automated testing - DBWS to be included in nightly test runs
 
** Automated testing - DBWS to be included in nightly test runs
−
*** Started
+
** PL/SQL Collection support.  This is being developed in 1.1 stream but will not be fully completed for this release.
−
** DBWSBuilder utility should auto-detect optimistic lock field
+
** [[EclipseLink/Development/DBWS/OptLock|wiki page]]: Auto-detection of optimistic lock field
−
*** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=249600 bug 249600], created a [[EclipseLink/Development/DBWS/OptLock|wiki page]] for it
+
*** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=249600 bug 249600], on hold for 1.1, pending PL/SQL Collection support
−
*** Started
+
 
* [http://wiki.eclipse.org/EclipseLink/Features/SDO SDO]
 
* [http://wiki.eclipse.org/EclipseLink/Features/SDO SDO]
 
** SDO2.1 is spec compliant (there is no TCK associated with this spec)
 
** SDO2.1 is spec compliant (there is no TCK associated with this spec)
 
** SDO2.1.1 feature complete.  Focus is on ensuring the most recently published TCK passes.  A public draft of SDO2.1.1 is due to be released in Nov 2008, but the spec is unlikely to be finalized before EclipseLink1.1.0 is released.
 
** SDO2.1.1 feature complete.  Focus is on ensuring the most recently published TCK passes.  A public draft of SDO2.1.1 is due to be released in Nov 2008, but the spec is unlikely to be finalized before EclipseLink1.1.0 is released.
−
*** TCK version: 2008-09-29
+
*** TCK version: 2008-10-06
 
*** Tests run: 403
 
*** Tests run: 403
−
*** Failures: 18
+
*** Failures: 7
−
*** Errors: 16
+
*** Errors: 6
 
* [http://wiki.eclipse.org/EclipseLink/Development/MOXy MOXy]
 
* [http://wiki.eclipse.org/EclipseLink/Development/MOXy MOXy]
 
** No major work items remain for this release.  Closing down assigned bugs.
 
** No major work items remain for this release.  Closing down assigned bugs.

Revision as of 16:05, 19 November 2008


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 19 2008

2PM EST, Wednesday Nov 19, 2008

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

Status updates

  • EclipseLink 1.1 proposed date push out - Feb 04 2009
    • Reasoning
      • SDO spec complete
      • Bug fixes
      • More JPA 2.0 features complete
    • Proposed schedule
      • 1.1.0M4 11/17/2008 Nov Milestone for 1.1.0
      • 1.1.0M5 12/09/2008 Dec Milestone for 1.1.0
      • 1.1.0M6 01/14/2009 Code Freeze - RC1 Jan Milestone for 1.1.0
      • 1.1.0M7 01/21/2009 RC2 Jan Milestone for 1.1.0
      • 1.1.0 02/04/2009 1.1.0 Released

1.1.0

  • JPA 2.0
  • DBWS
    • Automated testing - DBWS to be included in nightly test runs
    • PL/SQL Collection support. This is being developed in 1.1 stream but will not be fully completed for this release.
    • wiki page: Auto-detection of optimistic lock field
      • bug 249600, on hold for 1.1, pending PL/SQL Collection support
  • SDO
    • SDO2.1 is spec compliant (there is no TCK associated with this spec)
    • SDO2.1.1 feature complete. Focus is on ensuring the most recently published TCK passes. A public draft of SDO2.1.1 is due to be released in Nov 2008, but the spec is unlikely to be finalized before EclipseLink1.1.0 is released.
      • TCK version: 2008-10-06
      • Tests run: 403
      • Failures: 7
      • Errors: 6
  • MOXy
    • No major work items remain for this release. Closing down assigned bugs.

Bug Status

Foundation and JPA

Open Bugs

Note: We are in the middle of a clean-up of the 1.1 bugs. 1.1 bugs that are not set as P2 will have their target changed to a later release before next meeting.

Date 1.0.x 1.1 P2 1.1 P3 2.0 Untargetted
November 19, 2008 0 12 63 @ 29 @ 32
November 12, 2008 0 11 90 43 34
November 5, 2008 0 9 87 44 35
October 29, 2008 0 9 87 40 33
October 22, 2008 4 4 86 31  ?

@ Change due to bug clean-up and removal of enhancements from count.

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

1.1 Open

2.0 Open

Untargetted

Resolved Bugs previous week

Date 1.0.x 1.1 Invalid Duplicate Submitted Patch
November 19, 2008 0 7 3 1 3
November 12, 2008 0 3 3 0 0
November 5, 2008 0 5 1 0 0
October 29, 2008 2 5 1 1 1
October 22, 2008 4 7 2 2 3

Resolved Bugs

New Bugs previous week

Date Targetted 1.0.x Targetted 1.1 Targetted 2.0 Future Enhancement simple_fix build more info requested Already resolved
November 19, 2008 0 2 5 2 0 0 1 1 1
November 12, 2008 0 2 0 4 3 0 1 1 3
November 5, 2008 0 4 3 2 8 0 1 1 3
October 29, 2008 0 7 1 1 7 0 0 0 2
October 22, 2008 0 4 6 2 4 1 2 1 5

Created Bugs

General Issues

  • Action: add the 1.1.1 target milestones to bugzilla
  • Build Issues
    • Status:
      • Core build reworked. (added bundle creation, dependency existence testing, implement strategy for 3 build scenarios).
      • Looking at MW, and will start testing soon.
      • Build Reorg Status
        • Splitting work into Phase I and Phase II
          • Phase I complete: Product build changes, and sufficient changes in testing to run a nightly build end-to-end.
            • Patch awaiting review.
          • Phase II will wait until after notifications and other work completed.
      • Build Notifications
        • No Status change.
        • Initial investigation looks good.
        • Need to identify what feeds are needed. (automated success & failure) or divisions for each build type as well?
  • Bug DB usage

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

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

Back to the top