Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Development"
(linked to doc plan) |
(→Project Status/News) |
||
Line 50: | Line 50: | ||
* [[EclipseLink/Timeline | Project Timeline]] | * [[EclipseLink/Timeline | Project Timeline]] | ||
* [[EclipseLink/RoadMap | Project Road Map]] | * [[EclipseLink/RoadMap | Project Road Map]] | ||
− | |||
* [[EclipseLink/Building| Building EclipseLink]] | * [[EclipseLink/Building| Building EclipseLink]] | ||
* [[EclipseLink/Development/SprintList | Task List]] | * [[EclipseLink/Development/SprintList | Task List]] | ||
Line 63: | Line 62: | ||
=== 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 | + | 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. |
== Features and Enhancements == | == Features and Enhancements == |
Revision as of 16:04, 21 November 2007
Welcome to the Eclipse Persistence Services Project (EclipseLink) Development HomeThis page is focussed on information about current development and development process for the comitters of the EclipseLink project. |
LinksNewsgroups & Mailing Lists
BlogsDevelopment Documents |
|
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. The task list is the work that is done in a Sprint, organized by component.
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).