Difference between revisions of "EclipseLink/Development"

From Eclipsepedia

Jump to: navigation, search
Line 46: Line 46:
  
 
=== EclipseLink Development Process ===
 
=== EclipseLink Development Process ===
The development process for working on EclipseLink is based on the agile development process [http://en.wikipedia.org/wiki/Scrum_(development) Scrum].  In a nutshell, a prioritized [[EclipseLink/Development/Backlog|backlog]] is created and kept up to date using input from the community.  The [[EclipseLink/Development/SprintList|task list]] is the work that is done in a Sprint, organized by component.
+
The development process for working on EclipseLink is based on the agile development process [http://en.wikipedia.org/wiki/Scrum_(development) Scrum].  In a nutshell, a prioritized [[EclipseLink/Development/Backlog|backlog]] is created and kept up to date using input from the community.
  
 
=== Features and Enhancements ===
 
=== Features and Enhancements ===
Line 63: Line 63:
 
<table><tr><td style="background-color: #bbbad2; border-width: 1px; border-style: solid; border-color: #fabd23; padding: 10px;">
 
<table><tr><td style="background-color: #bbbad2; border-width: 1px; border-style: solid; border-color: #fabd23; padding: 10px;">
 
=== Links ===
 
=== Links ===
 +
* [EclipseLink/Development/2.1.0 | 2.1.0 Release Planning]
 
* [http://www.eclipse.org/eclipselink EclipseLink Home]
 
* [http://www.eclipse.org/eclipselink EclipseLink Home]
 
* [http://www.eclipse.org/eclipselink/downloads/index.php Downloads]
 
* [http://www.eclipse.org/eclipselink/downloads/index.php Downloads]

Revision as of 12:00, 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.

Project Status/News

Component Development Information/Status

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