Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Development"

(Project Status/News)
Line 55: Line 55:
 
** [[EclipseLink/Building | Working on building]]
 
** [[EclipseLink/Building | Working on building]]
 
* [[EclipseLink/IPLog | IP Log]]
 
* [[EclipseLink/IPLog | IP Log]]
 +
* [[EclipseLink/DevMeetings| Developer Meetings minutes and agendas]]
 
* [[EclipseLink/Timeline | Project Timeline]]
 
* [[EclipseLink/Timeline | Project Timeline]]
 
* [[EclipseLink/RoadMap | Project Road Map]]
 
* [[EclipseLink/RoadMap | Project Road Map]]

Revision as of 16:03, 2 October 2007

Welcome to the Eclipse Persistence Services Project (EclipseLink) wiki home

The EclipseLink project provides a runtime persistence solution focussed on leading standards and extended functionality needed for today's enterprise Java and SOA application development. EclipseLink offers support for:

EclipseLink is a sub-project of the Technology Project and is currently in its incubation phase.

Links

Newsgroups & Mailing Lists

Blogs

User Documents

Development Documents

Project Status/News

Articles

EclipseLink Development Process

The development process for working on EclipseLink is based on the agile development process Scrum. 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

design doc template

Back to the top