Jump to: navigation, search

Difference between revisions of "EclipseLink/Development"

(Project Status/News)
(Component Development Information/Status)
Line 48: Line 48:
 
<tr>
 
<tr>
 
<td>
 
<td>
=== Component Development Information/Status ===
 
  
* [[EclipseLink/Development/JPA | JPA]]
 
* [[EclipseLink/Development/MOXy | MOXy]]
 
* [[EclipseLink/Development/SDO | SDO]]
 
* [[EclipseLink/Development/DBWS| DBWS]]
 
  
 
=== EclipseLink Development Process ===
 
=== EclipseLink Development Process ===

Revision as of 15:25, 9 December 2009

Welcome to the Eclipse Persistence Services Project (EclipseLink) Development Home

This page is focussed on information about current development and development process for the comitters of the EclipseLink project.

Status/News

  • 2.0.1 Patch Set
    • Release Date not confirmed
  • 2.1.1 ?
  • 1.1.4 ?


EclipseLink Development Process

The development process for working on EclipseLink is based on the agile development process Scrum. In a nutshell, a prioritized backlog is created and kept up to date using input from the community.

Features and Enhancements

Features and Enhancements will have a BugZilla enhancement associated with it. A functional specification and design document will be created for each each feature. A review of these docs will be initially done by mailing list (eclipselink-dev@eclipse.org) and by meeting if followup is required. Prior to code being checked in, code reviews will be done through the mailing list (eclipselink-dev@eclipse.org).

Bugs

Docs are usually not required for bug fixes. Prior to code being checked in, code reviews will be done through the mailing list (eclipselink-dev@eclipse.org).

Links

Newsgroups & Mailing Lists

Blogs

Development Documents