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.
Difference between revisions of "Dali Meeting Minutes/Minutes20100621"
(→Dali Indigo (3.0?) Planning Meeting) |
(→Challenges) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 42: | Line 42: | ||
**Large project support | **Large project support | ||
**Quick Fixes | **Quick Fixes | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
+ | ===Challenges=== | ||
+ | *Complex JPA 2.0 concepts mixed with: | ||
+ | **Multi-version | ||
+ | **Multi-platform | ||
+ | **Multiple metadata sources | ||
+ | **Extensible | ||
===Priorities=== | ===Priorities=== | ||
Line 85: | Line 85: | ||
− | === Contributions | + | === Contributions === |
*Entity Diagram Editor (SAP) | *Entity Diagram Editor (SAP) | ||
− | + | *Package-level annotation support(JBoss) | |
===Notes=== | ===Notes=== |
Latest revision as of 17:34, 29 July 2010
Contents
Dali Indigo (3.0) Planning Meeting
June 21st, 2010 14:00 UTC
Attendees: Neil, Karen, Shaun, Paul, Brian, Tran, Nan
Agenda
- Retrospective
- Determine themes for Dali Indigo release
- Prioritize features in the various themes
- Discuss any new enhancement requests
- Ad-hoc items
Retrospective
- Good
- Scrapped the mid year release, which allowed more complete JPA 2.0 support to be delivered
- Model is holding up fairly well to new platforms and spec versions
- Looking at EclipseLink test models to find corner cases
- Perhaps EL should link to related test model from bug or wiki spec
- Bad
- Translators continue to be problematic, but saw some incremental improvements this year
- More wiki specs would be helpful, where description in the bug isn’t sufficient
- More involvement with review on EclipseLink features
- Should join the spec committee from tooling side
- Eclipse infrastructure continues to be slow, but manageable
- Builds - Full WTP build still fails too often, and is slow.
- One option is to move to independent Hudson
Themes
- Core enhancements
- Improved validation
- JDT refactoring participation
- Facet/Project creation
- JPQL Code Completion
- JAXB/O-X Mapping support
- EclipseLink Indigo support
- Usability
- Large project support
- Quick Fixes
Challenges
- Complex JPA 2.0 concepts mixed with:
- Multi-version
- Multi-platform
- Multiple metadata sources
- Extensible
Priorities
- JAXB/MOXY - 1
- EclipseLink mapping file overrides - 1
- Improved validation - 1
- JDT refactoring participation (basic cases) – 1
- Quick fixes (basic cases) - 1
- Utility Facet Removal/Project creation /OSGi/Maven - 1
- Facet Installation – how can we improve this
- Concurrency issues (Brian’s work) - 1
- Internal XML persistence (Sapphire/EMF Store/Translators) - 2
- EclipseLink native support - 2
- JPQL code completion / query editor / validation – 2
- Run JPQL queries - 3
- Remaining JPA 2.0 functionality
- ElementCollection - 1
- Embeddable access type – 2
- Others - 2
- Multiple PU support (still low priority) - 3
- Cross project persistence unit - 2
- Tabbed properties integration - 3
- Entity diagram editor - 1
- Package level annotations - 1
- Contributing target bundles into JEE package (EclipseLink) - 1
New requirements
- JAXB/MOXY support
Feature backlog
Contributions
- Entity Diagram Editor (SAP)
- Package-level annotation support(JBoss)
Notes
- Participation in JPA spec, is this helpful?
- Seems this would be nice at least as a way to get deeper understanding of feature set
- Would also be able to provide feedback directly into the committee
- Let’s try to get someone on the spec committee for next spec revision
- Perspective vs views…perhaps we should be asking if we should add our views to the current perspective.