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"

m (Agenda May 14 2008)
Line 14: Line 14:
 
* Bug Updates:
 
* Bug Updates:
 
** [http://wiki.eclipse.org/EclipseLink/Development/Bugs Bug Queries and other useful links]
 
** [http://wiki.eclipse.org/EclipseLink/Development/Bugs Bug Queries and other useful links]
** Open for 1.0: 54
+
** Open for 1.0: 56
** 13 Opened in 1.0 this week.
+
** 17 Opened in 1.0 this week.
** 19 closed in 1.0 - good job
+
** 33 closed in 1.0 - good job
  
 
Graph last updated Apr 30
 
Graph last updated Apr 30
Line 31: Line 31:
 
**** 1.0 is a bug that is to be fixed by 1.0, but has no current target milestone.
 
**** 1.0 is a bug that is to be fixed by 1.0, but has no current target milestone.
 
**** 1.0.1 new bugs should be filed against this target
 
**** 1.0.1 new bugs should be filed against this target
 +
* Bug council
 +
** Introduce notion of Bug council
 +
** Wed 2:30pm???
 +
** Need process to determine new bugs.
 +
 +
* Runtime Project
 +
** Move EclipseLink to runtime project.
 +
** Keep history except for newsgroups.
 +
 +
* Community
 +
** Eric Gwin - 2 days left in voting
 +
 +
* Code headers
 +
** Ensure Header is dual license EDL + EPL
 +
** Ensure contributor is correct - new code should have code author (no - intial code from oracle)
  
 
==== 1.0M8 ====
 
==== 1.0M8 ====
 
* Milestone release Date - June 4 2008 Final functionality freeze
 
* Milestone release Date - June 4 2008 Final functionality freeze
* 23 Open bugs
+
* 12 Open bugs
* 17 fixed
+
* 34 fixed
 
* Foundation and JPA Status
 
* Foundation and JPA Status
 
** Deployment XML rework
 
** Deployment XML rework

Revision as of 14:56, 28 May 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 May 28 2008

2PM EST, Wednesday May 28, 2008

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

Status updates

Graph last updated Apr 30

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.
      • Confusion/concern on this part
      • Milestones
        • 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.
        • 1.0.1 new bugs should be filed against this target
  • Bug council
    • Introduce notion of Bug council
    • Wed 2:30pm???
    • Need process to determine new bugs.
  • Runtime Project
    • Move EclipseLink to runtime project.
    • Keep history except for newsgroups.
  • Community
    • Eric Gwin - 2 days left in voting
  • Code headers
    • Ensure Header is dual license EDL + EPL
    • Ensure contributor is correct - new code should have code author (no - intial code from oracle)

1.0M8

  • Milestone release Date - June 4 2008 Final functionality freeze
  • 12 Open bugs
  • 34 fixed
  • Foundation and JPA Status
    • Deployment XML rework
      • Bug to merge xml working - clean-up started
  • OSGi - Tom
    • Wiki - http://wiki.eclipse.org/EclipseLink/Development/EclipseLinkPDEConversionPlan
    • PDE Projects available, eclipselink plugins in maven and jar containing all plug-ins available for download
    • Dynamic weaving in Equinox work underway
    • Initial planning for testing underway
    • Discussion
      • Packaging convention for dependancies (i.e. the projects we depend on that are not from Orbit)
        • Do we want a src and bin/classes directory
        • Should classes just exist at the base of the project (what about the jar we eventually create)
        • How should we name the jars we create
  • 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)
  • MOXy, JAXB, SDO - Blaise D
  • DBWS - Mike N
  • Build System
  • Documentation Status - Rick S
    • Complete User's Guide available. Minor/final cleanup remaining, as needed.

1.0 Release

  • Exit Criteria
    • 1.0M8 June 4, 2008 Final functionality freeze
    • 1.0RC1 June 11, 2008 Release Candidate 1
    • 1.0RC2 June 18, 2008 Release Candidate 2
    • 1.0 Release July 9, 2008 Final 1.0 Release (moved from june 25th to be released after Ganymede)
    • Schedule Dependencies
      • Eclipse reviews: graduation, release, and move to RT
      • Ganymede to leverage Equinox 3.4 (June 25)
  • 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
    • COMPLETE IP Log - Peter
    • 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

General Issues

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

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

  • 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
  • Bug Prioritization and targetting
    • Currently more bugs are scheduled for 1.0.1 then we are likely to fix in that time
    • We currently do not have a system to ensure a bug has a published priority level
    • We should discuss how will we deal with these issues

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

Eclipse 3.4 EE Ganymede M6 20080212

Eclipse 3.4 EE Ganymede M7 20080515

Back to the top