Difference between revisions of "EclipseLink/Development"

From Eclipsepedia

Jump to: navigation, search
m (Committer Resources)
m (Committer Resources)
Line 57: Line 57:
 
** [[EclipseLink/Development/Documentation|End-user documentation plan]]
 
** [[EclipseLink/Development/Documentation|End-user documentation plan]]
 
** [[EclipseLink/Building| Building EclipseLink]]
 
** [[EclipseLink/Building| Building EclipseLink]]
** [[EclipseLink/Design_Philosophy| Design Philosophy]]
+
<!--** [[EclipseLink/Design_Philosophy| Design Philosophy]]-->
  
 
* [[EclipseLink/IPLog | IP Log]] where all external contributions and new approved dependencies must be tracked
 
* [[EclipseLink/IPLog | IP Log]] where all external contributions and new approved dependencies must be tracked

Revision as of 19:45, 21 July 2010

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.1.1 Patch Set - Status: Proposed: Aug 2010
    • Development being done in /svnroot/rt/org.eclipse.persistence/branches/2.1/trunk/
  • 2.0.3 Patch Set - Status: Proposed: Fall , 2010
    • Development being done in '/svnroot/rt/org.eclipse.persistence/branches/2.0/trunk/
  • 1.1.4 Patch Set - Status: Started, Release Date Not Scheduled
    • Development being done in /svnroot/rt/org.eclipse.persistence/branches/1.1.0/trunk/
  • 1.2.1 Patch Set - Status: Not Scheduled
    • Development being done in /svnroot/rt/org.eclipse.persistence/branches/1.2/trunk/


Features, Bugs & 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).

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

Committer Resources

  • IP Log where all external contributions and new approved dependencies must be tracked
  • FishEye provides a graphical interface to monitor the SVN repository
  • Incubator where experimental ideas are developed

EclipseLink Newsgroups & Mailing Lists

Weekly Committer Meeting

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

Links