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"
(→Links) |
(→Links) |
||
Line 13: | Line 13: | ||
* [http://www.eclipse.org/eclipselink EclipseLink Home] | * [http://www.eclipse.org/eclipselink EclipseLink Home] | ||
* [[/Testing|Testing]] | * [[/Testing|Testing]] | ||
+ | * [[/Performance|Performance]] | ||
* [[:Category:EclipseLink]] | * [[:Category:EclipseLink]] | ||
* [[:Category:EclipseLink:Users]] | * [[:Category:EclipseLink:Users]] |
Revision as of 17:04, 3 December 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. |
Links
Newsgroups & 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).