EclipseLink/Development

From Eclipsepedia

Jump to: navigation, search

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 scheduled
  • 2.1.1 Patch Set
    • Release Date not scheduled
  • 1.1.4 Patch Set
    • Release Date not scheduled

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

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

Weekly Committer Meeting

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

Links