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"

(Resources)
(Current Development)
Line 20: Line 20:
 
* Development has moved from SVN to Git, see [[EclipseLink/Development/Process/Git|Git]]
 
* Development has moved from SVN to Git, see [[EclipseLink/Development/Process/Git|Git]]
  
 +
* [[EclipseLink/Development/2.6.0]]
 
* [[EclipseLink/Development/2.5.0]]
 
* [[EclipseLink/Development/2.5.0]]
 
** Looking for feedback on Proposals, Themes
 
** Looking for feedback on Proposals, Themes

Revision as of 13:34, 29 May 2013

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

  • Development has moved from SVN to Git, see Git
  • 2.2.1 Path Set
    • Development being done in /svnroot/rt/org.eclipse.persistence/branches/2.2/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 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

  • Testing
  • Performance
  • Incubator - where experimental ideas are developed
  • Development Process - overview of development process
  • IP Log - where all external contributions and new approved dependencies must be tracked
  • Building - building EclipseLink including Orbit projects
  • Maven - information about EclipseLink Maven repository
  • Git - Git source repository
  • Source - links to source code

Resources

  • git.eclipse - EclipseLink Git repository on Eclipse
  • FishEye - graphical interface monitoring the Git repository
  • Ohloh - open source project network

Development Documentation

Wiki

Back to the top