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"

Line 58: Line 58:
 
</td>
 
</td>
  
<td rowspan="2" width="310" valign="top">
+
<td rowspan="3" width="310" valign="top">
 
<table>
 
<table>
 
<tr><td style="background-color: #cff8d9; border-width: 1px; border-style: solid; border-color: #fabd23; padding: 10px;">
 
<tr><td style="background-color: #cff8d9; border-width: 1px; border-style: solid; border-color: #fabd23; padding: 10px;">

Revision as of 14:03, 16 September 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.2 -
    • Looking for feedback on Proposals, Themes
    • Development being done in /svnroot/rt/org.eclipse.persistence/trunk/
  • 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).

EclipseLink Newsgroups & Mailing Lists

Weekly Committer Meeting

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

Links

Resources

  • FishEye - graphical interface monitoring the SVN repository
  • Ohloh - open source project network

Development Documentation

Wiki

Copyright © Eclipse Foundation, Inc. All Rights Reserved.