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.
- Oct 9, 2009 - EclipseLink 1.1.3 Released!
- June 24, 2009 - EclipseLink 1.1.2 Released!
- May 15, 2009 - EclipseLink 1.1.1 Released!
- Mar 12, 2009 - EclipseLink 1.1 Released!
- Feb 4, 2009 - 1.1.0 RC1 available
- Jan 20, 2009 - 1.1.0 branch created for 1.1 release, trunk open for new 2.0 development.
- Oct 29, 2008 - EclipseLink 1.0.2 Released!
- Sept 9, 2008 - EclipseLink 1.0.1 Released!
- July 10, 2008 - 1.0.1 branch created for 1.0 patches, trunk open for new 1.1 development.
- July 9, 2008 - EclipseLink 1.0 Released!
- June 12, 2008 - Moving the EclipseLink project from Technology to RT. this will effect SVN, build, test, newsgroup, download locations.
- Feb 8, 2009 - Maven repository available
- Nov 12, 2007 - Nightly development builds, available for download.
- Aug 27, 2007 - All IPZilla bugs approved. Initial source contribution checked-in.
Component Development Information/Status
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 (firstname.lastname@example.org) and by meeting if followup is required. Prior to code being checked in, code reviews will be done through the mailing list (email@example.com).
Docs are usually not required for bug fixes. Prior to code being checked in, code reviews will be done through the mailing list (firstname.lastname@example.org).
- A way to query on what bug#'s correspond to the code checked into the nightly/milestone label so we can view the diffs as a transaction (individual diffs are available via SVN-update).
Newsgroups & Mailing Lists