Skip to main content
Jump to: navigation, search


EclipseLink Development Meeting 20080820

Minutes are preceeded by >

20 Aug 2008 Minutes


Krogh Peter;
Doughan Blaise;
O'Brien Michael;
Ware Tom;
Meswani Mitesh (Sun);
Elliot (Sun)
Sapir Rick;
Hauge Neil 


Agenda Aug 20 2008

2PM EST, Wednesday Aug 20, 2008

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

Status updates


  • Bug fixes
    • Release Sept 9
      • M1 - Aug 13th
        • Released
      • M2/RC - Aug 27th
      • Code Freeze - Aug 27th

>Mitesh? What time would the build come out? >If would be good if the GlassFish label picks up Tom's fix.

>A: we usually start building around 1400EDT on Wed. >We could build earlier, or you could use a nightly build if the fix is in.


  • Release December
    • JPA 2.0
    • Monthly Milestones Starting Aug 13th?

> built on 13th, went up on the 15th

1.0.1 bugs

>Triaged yesterday, if anyone else can triage the priority of these bugs and let Peter know if any are missing from the list or should be moved

General Issues

  • WIKI Changes should be done in parallel to any bug fixes to eclipselink.*.test ant targets or other public API changes - mobrien 20080529.
  • DONE Bugzilla components - sign-off on final changes below

  • 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
  • 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.0M9 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
      • Untargeted bugs are going to be reviewed by bug council on a weekly basis (current proposed time is directly after weekly status meeting (2:30 ET on Wednesdays).
        • A milestone will be set - or set to future
        • Bug may get assigned
      • When you enter a new bug, leaving it untargeted means that the bug council will review to decide which release it is targeted for.
      • If you know which milestone the bug will be fixed in, assign it accordingly.
      • The new target - future - is for bugs that don't have a target yet.
  • Code headers
    • Ensure Header is dual license EDL + EPL
      • Found and fxed some build xml files.
    • Ensure contributor is correct - new code should have code author (no - intial code from oracle)
      • Found and fxed some build xml files.

Upcoming Issues

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

Back to the top