Jump to: navigation, search

Difference between revisions of "EclipseLink/Development"

(Committer News)
Line 35: Line 35:
 
<tr>
 
<tr>
 
<td style="border-width: 1px; border-style: solid; border-color: #999999; padding: 10px;">
 
<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!]
+
=== EclipseLink Development Process ===
* Oct 9, 2009 - [http://www.eclipse.org/eclipselink/downloads/ EclipseLink 1.1.3 Released!]
+
* Mar 12, 2009 - [http://www.eclipse.org/eclipselink/downloads/ EclipseLink 1.1 Released!]
+
* Oct 29, 2008 - [http://www.eclipse.org/eclipselink/downloads/ EclipseLink 1.0.2 Released!]
+
* July 9, 2008 - [http://www.eclipse.org/eclipselink/downloads/ 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 - [[EclipseLink/Maven | Maven repository available]]
+
* 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.
+
</td>
+
</tr>
+
</table>
+
</td>
+
</tr>
+
  
<tr>
 
<td>
 
 
 
=== 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 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.
  

Revision as of 14:43, 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 ?


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).

Weekly Committer Meeting

  • Agenda
  • Thursday @ 11 AM EST (GMT -5)

Links

Newsgroups & Mailing Lists

Blogs

Development Documents