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"
Line 56: | Line 56: | ||
* [[EclipseLink/Timeline | Project Timeline]] | * [[EclipseLink/Timeline | Project Timeline]] | ||
* [[EclipseLink/RoadMap | Project Road Map]] | * [[EclipseLink/RoadMap | Project Road Map]] | ||
+ | |||
+ | </td> | ||
+ | </tr> | ||
+ | </table> | ||
=== EclipseLink Development Process === | === EclipseLink Development Process === | ||
Line 66: | Line 70: | ||
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> | </td> | ||
</tr> | </tr> |
Revision as of 12:25, 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 |
EclipseLink Development ProcessThe 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 EnhancementsFeatures 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). BugsDocs 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). |