EclipseLink/Development/DevMeetings/20080827

EclipseLink Development Meeting 20080827

Minutes are preceeded by >

27 Aug 2008 Minutes

---

Attendees:

Krogh Peter;
Twelves David;
Doughan Blaise;
O'Brien Michael;
Smith Shaun 
Ware Tom;
Meswani Mitesh (Sun);
Elliot (Sun)
Pelletier Guy;
Striffler Roger;
Norman Michael;
Sapir Rick;
Clarke Doug;
Hauge Neil 

Actions:

---

>Action: Peter: Double check changes in iplog affect trunk and not our 1.0.1 branch >Action: Does everyone agree with these code freeze definitions (Mon is a holiday) >Action: All: Anything assigned as low rick - take action to defer it

Agenda Aug 27 2008

2PM EST, Wednesday Aug 27, 2008

1.0.1

• Release Review
  • Not requied on minor releases

>Neil: WTP does not do them, process doc says only major releases >As long there is no new functionality introduced >Action: Peter: Double check changes in iplog affect trunk and not our 1.0.1 branch

• Bug fixes
  • Release bits build - Sept 9
    • M2/RC - Aug 27th

>Tom: The core tests passed, JPA tests are in progress - after DB problem this morning >Last nights nightly went very well - but the difference between the two is very minimal (16 modifications)

• • • Code Freeze - Aug 27th
    • RC2 build sept 3

code freeze definition

• RC1 - Aug 27th
  • No risky fixes
• RC2 - Sept 3
  • Only Regressions.

>Action: Does everyone agree with these code freeze definitions (Mon is a holiday)

1.1

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

>Continue to work on design for extended map support >Will pick up more JPA 2.0 features

1.0.1 bugs

• 21 Bugs OPEN - All Components

>Action: All: Anything assigned as low rick - take action to defer it >The unassigned bugs will be deferred >Rick is addressing the doc bugs >Neil: A blocker for MW - it is unable to start - Les currently investigating/fixing - let us know the workaround

• 60 Bugs CLOSED - All Components

General Issues

>DBWS:JDK16> >DBSW/DBWS tests not being added to the build - Blocker JDK 1.6 is required at runtime >Action: add a bug to use 1.6 and compile as target 1.5 - starting next release after 1.0.1 >There is a bug/designdoc and wiki page for 1.6 >A lot of our dependent jars will go away after the 1.6 switch

• 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

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
• 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.

• EclipseLink/Development/Examples: Strategy for the development and maintenance of examples
• EclipseLink/Development/OSGi: Strategy for delivery of OSGi/Equinox bundles
• EclipseLink/Development/JPA_2.0: Strategy for the concurrent development of JPA 2.0 while maintaining JPA 1.0 usage
• EclipseLink/Development/Spring: Strategy for using EclipseLink within the Spring Framework
• EclipseLink/Development/Java6: Strategy for using EclipseLink on a Java SE 6 JRE