Skip to main content
Jump to: navigation, search

EclipseLink/Development

< EclipseLink
Revision as of 14:25, 28 August 2007 by Peter.krogh.oracle.com (Talk | contribs) (New page: === Eclipe Persistence Services Development === This is the landing page for all things development. === EclipseLink Development Process === The development process for working on Eclip...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Eclipe Persistence Services Development

This is the landing page for all things development.

EclipseLink Development Process

The development process for working on EclipseLink is based on the agile development process [1]. In a nutshell, a prioitized backlog is created and kept up to date using input from the community. The task list is the work that is done in a Sprint, organized by componant.

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 note required for bug fixes. Prior to code being checked in, code reviews will be done through the mailing list (eclipselink-dev@eclipse.org).

Design Docs

ORM

Back to the top