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"
(→Links) |
|||
| Line 56: | Line 56: | ||
* [[EclipseLink/Timeline | Project Timeline]] | * [[EclipseLink/Timeline | Project Timeline]] | ||
* [[EclipseLink/RoadMap | Project Road Map]] | * [[EclipseLink/RoadMap | Project Road Map]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=== 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 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. | 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 === |
Features and Enhancements will have a BugZilla enhancement associated with it. A functional specification and [[EclipseLink/Development/DesignDocs|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). | Features and Enhancements will have a BugZilla enhancement associated with it. A functional specification and [[EclipseLink/Development/DesignDocs|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 == | + | === 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). | 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). | ||
| + | |||
| + | </td> | ||
| + | </tr> | ||
| + | </table> | ||
| + | </td> | ||
| + | </tr> | ||
| + | </table> | ||
[[Category:EclipseLink|Development]] | [[Category:EclipseLink|Development]] | ||
Revision as of 12:22, 7 January 2008
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 |
|