Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Development"

(Links)
Line 19: Line 19:
 
<td style="background-color: #cff8d9; border-width: 1px; border-style: solid; border-color: #999999; padding: 10px;">
 
<td style="background-color: #cff8d9; border-width: 1px; border-style: solid; border-color: #999999; padding: 10px;">
  
== Status/News ==
+
== Current Development ==
 
* [[EclipseLink/Development/2.1]] - Planning our Helios Release
 
* [[EclipseLink/Development/2.1]] - Planning our Helios Release
 
** Looking for feedback on proposes Themes
 
** Looking for feedback on proposes Themes
Line 29: Line 29:
  
 
* 1.1.4 ?
 
* 1.1.4 ?
 +
 +
 +
</td>
 +
</tr>
 +
<tr>
 +
<td style="border-width: 1px; border-style: solid; border-color: #999999; padding: 10px;">
 +
== Committer News ==
  
 
* Oct 26, 2009 - [http://www.eclipse.org/eclipselink/downloads/ EclipseLink 1.2 Released!]
 
* Oct 26, 2009 - [http://www.eclipse.org/eclipselink/downloads/ EclipseLink 1.2 Released!]
Line 39: Line 46:
 
* Nov 12, 2007 - [http://www.eclipse.org/eclipselink/downloads/ Nightly development builds, available for download.]
 
* Nov 12, 2007 - [http://www.eclipse.org/eclipselink/downloads/ Nightly development builds, available for download.]
 
* Aug 27, 2007 - All IPZilla bugs approved. Initial source contribution checked-in.
 
* Aug 27, 2007 - All IPZilla bugs approved. Initial source contribution checked-in.
 
 
</td>
 
</td>
 
</tr>
 
</tr>

Revision as of 15:29, 9 December 2009

Welcome to the Eclipse Persistence Services Project (EclipseLink) Development Home

This page is focussed on information about current development and development process for the comitters of the EclipseLink project.

Current Development

  • 2.0.1 Patch Set
    • Release Date not confirmed
  • 2.1.1 ?
  • 1.1.4 ?


Committer News


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.

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 not required for bug fixes. Prior to code being checked in, code reviews will be done through the mailing list (eclipselink-dev@eclipse.org).

Links

Newsgroups & Mailing Lists

Blogs

Development Documents

Copyright © Eclipse Foundation, Inc. All Rights Reserved.