Jump to: navigation, search

Difference between revisions of "EclipseLink/Development"

m (Committer Resources)
m (Committer Resources)
Line 59: Line 59:
 
* [[EclipseLink/Development/Incubator|Incubator]] where experimental ideas are developed  
 
* [[EclipseLink/Development/Incubator|Incubator]] where experimental ideas are developed  
  
* Newsgroups & Mailing Lists  
+
==== EclipseLink Newsgroups & Mailing Lists ====
 
** [http://www.eclipse.org/forums/index.php?t=thread&frm_id=111 EclipseLink RT Newsgroup]
 
** [http://www.eclipse.org/forums/index.php?t=thread&frm_id=111 EclipseLink RT Newsgroup]
 
** [http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/maillist.html EclipseLink Dev Mailing list - eclipse.org hosted - date view]
 
** [http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/maillist.html EclipseLink Dev Mailing list - eclipse.org hosted - date view]

Revision as of 09:54, 28 May 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

  • EclipseLink/Development/2.1 - Planning our Helios Release
    • Looking for feedback on proposds Themes
    • Development being done in /svnroot/rt/org.eclipse.persistence/trunk/
  • 2.0.1 Patch Set - Status: Proposed: Feb 17, 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