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 43: | Line 43: | ||
== Project Status/News == | == Project Status/News == | ||
− | * | + | * Nov 12, 2007 - [http://www.eclipse.org/eclipselink/downloads/ Nightly development builds, available for download.] |
− | + | * Nov 5, 2007 - [http://www.eclipse.org/eclipselink/downloads/ 1.0M1 initial development milestone I completed, and available for download.] | |
− | + | * Aug 27, 2007 - All IPZilla bugs approved. Initial source contribution checked-in. | |
* [[EclipseLink/IPLog | IP Log]] | * [[EclipseLink/IPLog | IP Log]] | ||
* [[EclipseLink/DevMeetings| Developer Meetings minutes and agendas]] | * [[EclipseLink/DevMeetings| Developer Meetings minutes and agendas]] |
Revision as of 16:16, 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).