Difference between revisions of "EclipseLink/Development"

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

Revision as of 15:50, 9 December 2009

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 proposes Themes

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

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

Development Documentation

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

Newsgroups & Mailing Lists

Weekly Committer Meeting

Agenda
Thursday @ 11 AM EST (GMT -5)

@@ Line 37: / Line 37: @@
 <td>
-=== EclipseLink Development Process ===
+=== Features, Bugs & Enhancements ===
-The development process for working on EclipseLink is based on the agile development process [http://en.wikipedia.org/wiki/Scrum_(development) Scrum].  In a nutshell, a prioritized [[EclipseLink/Development/Backlog|backlog]] is created and kept up to date using input from the community.
-=== Features and Enhancements ===
 Features and Enhancements will have a BugZilla [[EclipseLink/Development/Bugs|enhancement]] associated with it.  A functional specification and [[EclipseLink/Development/DesignDocs|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 [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EclipseLink bug] fixes.  Prior to code being checked in, code reviews will be done through the mailing list (eclipselink-dev@eclipse.org).

Breadcrumbs