Skip to main content

Notice: This Wiki is now read only and edits are no longer 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)
(General Issues)
Line 145: Line 145:
 
* Build Issues  
 
* Build Issues  
 
** Status:
 
** Status:
*** Bugs 245394 & 239984 proposed changes to Version.class and change to three digit versions. Will be committing today or tomorrow.
+
*** Core build reworked. (added bundle creation, dependency existence testing, implement strategy for 3 build scenarios).
*** Bug 239513: Will modify build to include full mw build and test after have committed above. if it fits within a half hour, we will keep change.
+
*** Looking at MW, and will start testing soon.
** Discussion:
+
*** Build Reorg Discussion
*** Can we please remove checked in Derived Objects (built files) from our process? Examples are OK. They are not part of regular build.
+
**** Any concerns?
**** Causing merge conflicts on build machine (ok now, but may not be later)
+
**** If not, hope to have patch available end-of-week
**** Revision of built object is NOT guaranteed to contain the source that built it.
+
*** Build Notifications
**** Causes conflicted updates locally (must rename or delete files to proceed correctly).
+
**** Mike found source for an ant notify that publishes to RSS
**** Once we have revision number linked to the build files, there is little need. periodic backups of all milestones would accomplish stated goal without the side-effects.
+
**** Initial investigation looks good. Just need to identify what feeds are needed. (automated success & failure) or divisions for each build type as well?
 
* Bug DB usage
 
* Bug DB usage
 
** See wiki page http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines
 
** See wiki page http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines

Revision as of 13:08, 5 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 Oct 22 2008

2PM EST, Wednesday Oct 22, 2008

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

Status updates

  • Roadmap in a new plan format
    • upcoming dates
      • 1.0.2M1 Complete 10/15/2008 M1 Milestone for 1.0.2
      • 1.1.0M3 Complete 10/17/2008 Oct Milestone for 1.1.0
      • 1.0.2M2 Today 10/22/2008 RC Milestone for 1.0.2
      • 1.0.2 final build. 10/22/2008.
      • 1.0.2 10/29/2008 1.0.2 Released
      • 1.1.0M4 11/17/2008 Nov Milestone for 1.1.0
      • 1.1.0M5 11/26/2008 RC1 Milestone for 1.1.0
      • 1.1.0M6 12/03/2008 RC2 Milestone for 1.1.0
      • 1.1.0 12/09/2008 1.1.0 Released

1.1.0

  • Release December
    • JPA 2.0
    • DBWS
      • First release of the Database Web Service (DBWS) component
      • Automated testing - DBWS to be included in nightly test runs
        • Started
      • DBWSBuilder utility should auto-detect optimistic lock field
    • 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-09-29
        • Tests run: 403
        • Failures: 18
        • Errors: 16
    • MOXy
      • No major work items remain for this release. Closing down assigned bugs.

Bug Status

1.0.2 bugs

open bugs

fixed bugs

Foundation and JPA

Open Bugs

Date 1.0.x 1.1 P2 1.1 P3 2.0 Untargetted
October 29, 2008 0 9 87 40 33
October 22, 2008 4 4 86 31 -

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 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 5, 2008 0 7 1 1 8 0 0 0 2
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.0 M3+ target milestones to bugzilla
  • Database consistency between 1.0.2 and 1.1.0. Caused build failures.
    • Different databases?
    • Better clean mechanism?
  • 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 Discussion
        • Any concerns?
        • If not, hope to have patch available end-of-week
      • Build Notifications
        • Mike found source for an ant notify that publishes to RSS
        • Initial investigation looks good. Just need to identify what feeds are needed. (automated success & failure) or divisions for each build type as well?
  • Bug DB usage
  • Bug Triage
    • 249338: Discuss response to why all detached and unreferenced objects must be merged and not just the owner and how this relates to section 3.2.4 point 1-2-2 p.70 of the JPA 2.0 spec, section 3.2.3 point 1-2-2 p.50 of the JPA 1.0 spec.

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