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.
Difference between revisions of "EclipseLink/Development"
(→Project Status/News) |
(→Project Status/News) |
||
Line 60: | Line 60: | ||
* [[EclipseLink/FAQ| EclipseLink FAQ]] | * [[EclipseLink/FAQ| EclipseLink FAQ]] | ||
* [[EclipseLink/Building| Building EclipseLink]] | * [[EclipseLink/Building| Building EclipseLink]] | ||
+ | * [[EclipseLink/Development/SprintList | Task List]] | ||
</td> | </td> | ||
</tr> | </tr> |
Revision as of 14:24, 4 October 2007
Welcome to the Eclipse Persistence Services Project (EclipseLink) wiki homeThe 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. |
LinksNewsgroups & Mailing Lists
BlogsUser DocumentsDevelopment Documents |
|
|
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).