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"

(→‎Minutes from Past Meetings)
Line 13: Line 13:
 
=== Status updates ===
 
=== Status updates ===
 
* Bug Updates:
 
* Bug Updates:
 +
** [http://wiki.eclipse.org/EclipseLink/Development/Bugs Bug Queries]
 
** Total Open: 218
 
** Total Open: 218
 
** Open for 1.0: 37
 
** Open for 1.0: 37

Revision as of 15:26, 16 April 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.

Agenda Apr 16 2008

2PM EST, Wednesday Apr 16, 2008

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

Status updates

  • Bug Updates:
    • Bug Queries
    • Total Open: 218
    • Open for 1.0: 37
      • Please look through untargetted open bugs, and let Peter K or Doug C know of any that are must haves.

Bug graph.PNG

  • Bug DB usage
    • If you are working on a bug, assign it to yourself.
      • add dummy inbox to the cc list.
    • Set the target milestone to the correct milestone.
      • Milestones
        • 1.0M7, 1.0M8 are bugs that are to be fixed by the the corresponding milestone build.
        • 1.0 is a bug that is to be fixed by 1.0, but has no current target milestone.
  • OSGi

1.0 Release

  • 1.0 Release Date: June 25th | details
    • Exit Criteria now documented. Please review and provide feedback on the dev mailing list - Doug
    • Schedule Dependencies
      • Eclipse reviews: graduation, release, and move to RT
      • Ganymede to leverage Equinox 3.4
  • Change in scope for 200040: Focus on new JPA usable XML file with key advanced features
    • Replacing existing XML schema, full mapping features, and migration deferred to the 1.1 release
  • JAXB2 compliance: Not complete for 1.0. Need to document exact support level and advanced features
  • Pre-release tasks
    • 3rd party works-with approval for Oracle JDBC - Doug
    • 1st pass Complete IP Log - Peter
      • Team leads please look through, and verify
    • Complete Features Index - Doug with support of all committers
    • Complete Examples & How-to materials - Doug/Shaun
    • FAQ
    • Update wiki Documentation for 1.0 Features - Liza (starting in May) with committer support
    • Finalize product packaging and distribution - ZIP(s), Bundle access (update site?)
    • Prepare and schedule reviews

1.0M7

  • Milestone release Date - May 7th
  • Foundation and JPA Status
    • Deployment XML rework
      • Bug to merge xml started, targetted for M8.
  • OSGi - Tom
    • moved from M6 219012: Make SDO compatible with OSGi
    • 221377: Convert EclipseLink Projects to PDE Projects and Rename
    • 221381: Update EclipseLink build to generate both EclipseLink.jar and bundle jars
    • 221379: Extract eclipselink.core.lib zips into separate PDE Projects
    • 221383: Move all files in eclipselink.core/resources under src
  • Workbench
    • Tested XML and EIS mapping functionality.
    • Able to open of toplink mapping workbench 10.1.3 projects
    • Corrected the issue with Cache Synchronization (replaced functionality erroneously removed)
  • OXM, JAXB, SDO - Blaise D
  • Documentation Status - Rick S
    • Complete User's Guide available. Minor/final cleanup remaining, as needed.

General Issues

  • DONE Bugzilla components - sign-off on final changes below

http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/msg00640.html

  • Test Failures
    • Tests that pass locally and fail on the build server are swamping Tom.
    • Generally these occur because of env differences (DB, VM etc..)
    • Need a strategy for solving these.
  • Automated Testing
    • Need SRG test models for JPA, MOXy and SDO
      • DB components of those tests should be simple enough to run on Derby
      • Need to test Core SRG on Derby


Upcoming Issues

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

Minutes from Past Meetings

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

Back to the top