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.
DaliMeetingMinutes20080714
Contents
Dali Post 2.0 Planning Meeting
July 14th, 2008
Attendees: Neil Hauge, Brian Vosburgh, Karen Butzke, Paul Fullbright, Tran Le, Shaun Smith
Post 2.0 Priorities/High level Release Planning (tentative)
- 2.1 (December 2008)
- EclipseLink support (what version, 1.0.1, 1.1?, would be nice to target 1.1 (Dec12)
- Looks like we will only be able to cover 1.0 features
- Case sensitivity
- Class file support
- Usability features
- EclipseLink support (what version, 1.0.1, 1.1?, would be nice to target 1.1 (Dec12)
- 2.2 (June 09)
- Public API? (depends on whether the API needs to change, solicit adopter feedback)
- Ships on WTP 3.1
- 3.0 (December 09) (very tentative)
- JPA 2.0
Review feature backlog, deferred items from 2.0
- Dali feature backlog post 2.0 (Reviewed and updated)
EclipseLink Support: Use cases/functional issues
- DaliEclipseLinkPlatform (Reviewed and Updated)
- Do we want to highlight EclipseLink specific features in the UI in the EclipseLink UI?
- Some sort of icon or symbol that identifies EclipseLink content
- Var 1:1 has lowest priority
- Need to be able to support spec orm.xml in EclipseLink platform
- This means we would need to be able to load a given UI for a given XML Mapping File schema; Generic or EclipseLink Mapping File UI.
- Support every mapping type in Embedded
Milestone Planning
- Option 1 (release in Dec ‘08)
- Pros: Earlier release, more time for 2.2
- Cons: Less support for EclipseLink features
- M1 – Aug 22nd
- M2 – Oct 3rd
- M3 – Nov 7th (Feature Freeze)
- RC1 - Dec 5th
- RC2 – Dec 12th
- Release – Dec 19th
- Options 2 (release in Jan ’09)
- Pros: More features
- Cons: Later release, less time for 2.2
- M1 – Aug 22nd
- M2 – Oct 3rd
- M3 – Nov 21th (Feature Freeze)
- RC1 - Jan 9th
- RC2 – Jan 16th
- Release – Jan 23th
Resource Planning
- M1
- Paul
- Load resource based on content type with any name
- Differently named orm.xml files
- Differentiate content type on schemas location
- Load resource based on content type with any name
- Karen
- EclipseLink Caching annotation support (potentially XML)
- Tran
- Remaining persistence.xml features
- Adding driver library on new project creation (need bug for this) (tentetavie)
- Build work
- Bug fixes for 2.0.1
- Brian
- Case sensitive DB support
- Neil
- Developer documentation
- Paul
- M2
- Resource model for EclipseLink Mapping File
- Binary Class support
- Converters (2-3 weeks)
- EclipseLink Attribute Mappings (1-2 weeks)
- Transformation
- M3
- EclipseLink Attribute Mappings (1-2 weeks)
- BasicMap
- BasicCollection
- EclipseLink Attribute Options: Private Owned, JoinFetch, Mutable (1 week)
- Advanced EclipseLink Options (1-2 weeks)
- Customizer
- Copying/Instantiation
- Read Only
- EclipseLink Locking (1 week)
- EclipseLink Attribute Mappings (1-2 weeks)