Jump to: navigation, search

Difference between revisions of "EclipseLink/Development/2.1"

(Requirements)
 
(37 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 
= EclipseLink 2.1 (Helios) Planning =
 
= EclipseLink 2.1 (Helios) Planning =
 +
 +
<div style="border: 3px red solid;" align="center" >Content moved to [http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipselink/project-info/plans/2_1_0.xml 2.1.0 Plan]</div>
  
 
'''Target Release Date: Helios (June 23, 2010)'''
 
'''Target Release Date: Helios (June 23, 2010)'''
Line 7: Line 9:
 
== Themes ==
 
== Themes ==
  
The following themes are being addressed for the 1.2.0 release with all feature working falling within these themes.
+
The following themes are the focus of the 2.1 release with the majority of effort falling under these themes.
  
 
=== Helios ===
 
=== Helios ===
  
This is the EclipseLink release that will go into the annual Eclipse Helios release. Some work will be required to ensure all of the release train requirements are met and that EclipseLink functions well within the IDE as well as within the RT platform. This work will involve addressing better OSGi/Equinox compatibility.
+
This is the EclipseLink release that will go into the annual Eclipse release named [[Helios]] scheduled for release on June 23rd 2010. Some work will be required to ensure all of the release train requirements are met and that EclipseLink functions well within the IDE as well as within the RT platform. This work will include addressing better OSGi/Equinox compatibility.
  
 
=== Community ===
 
=== Community ===
  
The last couple of release cycles have had a focus on major new feature areas (SDO, DBWS, JPA 2.0). This work has prevented the project team from keeping up with the community's request for enhancements and bug fixes. This release will endeavor to reduce the bug backlog to a more reasonable quantity.  
+
The last couple of release cycles have had a focus on major new feature areas (SDO, DBWS, JPA 2.0). This work has prevented the project team from keeping up with the community's request for enhancements and bug fixes. This release will endeavour to reduce the bug backlog to a more reasonable quantity.  
  
 
Continued improvements to usability focusing on simplified getting started steps as well as ability to find technical information on how EclipseLink works and how to solve both common and advanced requirements.
 
Continued improvements to usability focusing on simplified getting started steps as well as ability to find technical information on how EclipseLink works and how to solve both common and advanced requirements.
  
=== Metadata ===
+
Goals:
 +
* Address '''simple_fix''' issues - [https://bugs.eclipse.org/bugs/buglist.cgi?columnlist=bug_severity%2Cpriority%2Cassigned_to%2Cbug_status%2Cvotes%2Ctarget_milestone%2Ccomponent%2Cshort_desc;classification=RT;query_based_on=2.1;status_whiteboard_type=allwordssubstr;query_format=advanced;status_whiteboard=simple_fix;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;product=EclipseLink;known_name=2.1 bug query]
 +
* Address '''submitted_patch''' issues - [https://bugs.eclipse.org/bugs/buglist.cgi?columnlist=bug_severity%2Cpriority%2Cassigned_to%2Cbug_status%2Cvotes%2Ctarget_milestone%2Ccomponent%2Cshort_desc;classification=RT;query_based_on=2.1;status_whiteboard_type=allwordssubstr;query_format=advanced;status_whiteboard=submitted_patch;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;product=EclipseLink;known_name=2.1 bug query]
 +
* Bug Queries
 +
** [https://bugs.eclipse.org/bugs/buglist.cgi?order=Importance;columnlist=bug_severity%2Cpriority%2Cassigned_to%2Cbug_status%2Cvotes%2Ctarget_milestone%2Ccomponent%2Cshort_desc;classification=RT;query_based_on=2.1;query_format=advanced;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;product=EclipseLink;target_milestone=2.1;known_name=2.1 Bugs assigned to 2.1]
 +
** [https://bugs.eclipse.org/bugs/buglist.cgi?columnlist=bug_severity%2Cpriority%2Cassigned_to%2Cbug_status%2Cvotes%2Ctarget_milestone%2Ccomponent%2Cshort_desc;classification=RT;query_format=advanced;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;target_milestone=Future;product=EclipseLink Future Bugs ordered by Bugzilla's Importance]
  
Currently the EclipseLink project offers multiple metadata approaches for each persistence service. This release will focus on simplifying around simplifying the metadata approach used for each service ensuring that all necessary functionality is available.
+
=== Documentation ===
 +
 
 +
The EclipseLink 2.1 release will include a new set of documentation delivered in HTML and PDF formats. This effort is based on these [[EclipseLink/Development/Documentation/Requirements | requirements]]. The goal is to improve the usability of the documentation.
 +
 
 +
* [[EclipseLink/Development/Documentation/JPA | EclipseLink JPA User Guide]]
 +
* [[EclipseLink/Development/Documentation/MOXy | EclipseLink MOXy User Guide]]
  
 
=== Advanced ===
 
=== Advanced ===
  
With the completion of the JPA 2.0 implementation focused on delivering the reference implementation the project will now work on exposing additional advanced Object-Relational features through easy to use extensions to JPA that will enable users to easily and consistently consume them with minimal dependencies on native EclipseLink API.
+
In this release the project is planning to increase the advanced features available through standard API using common extension points, custom annotations, and extended XML configuration files. The goal is to enable users to work with the standards (JPA, JAXB, SDO) as much as possible and simplify the usage of advanced features.
  
=== Dynamic ===
+
* Advanced JPA
 +
** [[EclipseLink/Development/2.1/AdvancedJPA | Advanced mapping options]] available through custom annotations and/or eclipselink-orm.xml - {{bug|227219}}
 +
** [[EclipseLink/Development/2.1/AdvancedJPA_Queries | Query Extensions]] available through JPQL and Criteria API - {{bug|219814}}
 +
* Advanced MOXy (JAXB)
 +
** Complete JAXB mapping support in eclipselink-oxm.xml mapping file - {{bug|293925}}
 +
** Advanced mapping options available through custom annotations and/or eclipselink-oxm.xml - {{bug|296967}}
  
The 1.2.0 and 2.0.0 releases of EclipseLink introduced support for dynamic entities that could be mapped without requiring .java files being generated/compiled/packaged. This support will now be further extended to work with all of the applicable configuration models in MOxy and JPA including combining multiple mappings for the same entities. The now public infrastructure will also be coordinated with SDO and DBWS use of dynamic persistence.
+
== Work Complete ==
  
== Requirements ==
+
The following is intended to be a high level list of completed work towards this release
 +
* [https://bugs.eclipse.org/bugs/buglist.cgi?resolution=FIXED;classification=RT;query_format=advanced;bug_status=RESOLVED;bug_status=VERIFIED;bug_status=CLOSED;target_milestone=2.1;product=EclipseLink Fixed Bugs]
  
Based on the above theme the following requirements will be addressed for this release.
+
== Schedule ==
 +
 
 +
The 2.1 development and release schedule must align with the [[Helios]] schedule.
  
 
{|{{BMTableStyle}}
 
{|{{BMTableStyle}}
 
|-{{BMTHStyle}}
 
|-{{BMTHStyle}}
! Id
+
! Milestone
! Component
+
! Date
! Requirement
+
! Status
! Priority
+
! Notes
 
|-
 
|-
| Helios-1 || All || Meet Helios release train requirements || ?
+
| M1 || ? || Building || Target for Helios M4
|-
+
| Helios-2 || JPA || Upgrade weaving support to use Equinox Weaving  || ?
+
|-
+
| Community-1 || All || Reduce Bug/ER backlog <br> ''Backlog will be addressed based on priority, votes, patches supplied, and feasibility for the release time frame.  || ?
+
|-
+
| Community-2 || JPA  || Deliver new EclipseLink JPA documentation || ?
+
|-
+
| Metadata-1 || JPA || Provide access to all functionality from deployment XML in eclipselink-orm.xsd || ?
+
|-
+
| Metadata-2 || MOXy || Provide access to all functionality from deployment XML in eclipselink-oxm.xsd || ?
+
|-
+
| Metadata-3 || JPA/MOXy || Have the workbench generate eclipselink-orm and eclipselink-oxm as well as migrating from deployment XML ||
+
|-
+
| Advanced-1 || JPA || Extended JPA querying to support (JPQL & Criteria) || ?
+
|-
+
| Dynamic-1 || JPA || Enable dynamic JPA using eclipselink-orm.xsd || ?
+
|-
+
| Dynamic-2 || MOXy || Enable dynamic MOXy using eclipselink-oxm.xsd and API || ?
+
|-
+
| Dynamic-3 || JPA/MOXy || Enable dynamic models using both JPA and MOXy using XML and/or API configuration || ?
+
 
|-
 
|-
 
|}
 
|}
  
== Schedule ==
+
* [[Helios]] - Annual release milestones - June 23/2010
 +
** M1  - August 21/09: Included EclipseLink 1.1.3 M1
 +
** M2  - October 2/09: Included EclipseLink 1.1.3 RC1
 +
** M3+1 - November 9/09: No update (1.1.3 RC1)
 +
** M3  - November 13/09: Available
 +
** M4+1 - December 14/09: targeting inclusion of EclipseLink 1.1.3 GA or Trunk
 +
** M4  - December 18/09: Available
  
The 2.1 development and release schedule must align with the [[Helios]] schedule.
+
[[Category:EclipseLink_Dev_2.1|Release Plan]]
 +
[[Category:EclipseLink|Development/2.1]]

Latest revision as of 13:59, 24 October 2011

EclipseLink 2.1 (Helios) Planning

Content moved to 2.1.0 Plan

Target Release Date: Helios (June 23, 2010)

Themes

The following themes are the focus of the 2.1 release with the majority of effort falling under these themes.

Helios

This is the EclipseLink release that will go into the annual Eclipse release named Helios scheduled for release on June 23rd 2010. Some work will be required to ensure all of the release train requirements are met and that EclipseLink functions well within the IDE as well as within the RT platform. This work will include addressing better OSGi/Equinox compatibility.

Community

The last couple of release cycles have had a focus on major new feature areas (SDO, DBWS, JPA 2.0). This work has prevented the project team from keeping up with the community's request for enhancements and bug fixes. This release will endeavour to reduce the bug backlog to a more reasonable quantity.

Continued improvements to usability focusing on simplified getting started steps as well as ability to find technical information on how EclipseLink works and how to solve both common and advanced requirements.

Goals:

Documentation

The EclipseLink 2.1 release will include a new set of documentation delivered in HTML and PDF formats. This effort is based on these requirements. The goal is to improve the usability of the documentation.

Advanced

In this release the project is planning to increase the advanced features available through standard API using common extension points, custom annotations, and extended XML configuration files. The goal is to enable users to work with the standards (JPA, JAXB, SDO) as much as possible and simplify the usage of advanced features.

Work Complete

The following is intended to be a high level list of completed work towards this release

Schedule

The 2.1 development and release schedule must align with the Helios schedule.

Milestone Date Status Notes
M1  ? Building Target for Helios M4
  • Helios - Annual release milestones - June 23/2010
    • M1 - August 21/09: Included EclipseLink 1.1.3 M1
    • M2 - October 2/09: Included EclipseLink 1.1.3 RC1
    • M3+1 - November 9/09: No update (1.1.3 RC1)
    • M3 - November 13/09: Available
    • M4+1 - December 14/09: targeting inclusion of EclipseLink 1.1.3 GA or Trunk
    • M4 - December 18/09: Available