Component Development Information/Status
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. The task list is the work that is done in a Sprint, organized by component.
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 (email@example.com) and by meeting if followup is required. Prior to code being checked in, code reviews will be done through the mailing list (firstname.lastname@example.org).
Docs are usually not required for bug fixes. Prior to code being checked in, code reviews will be done through the mailing list (email@example.com).
- A way to query on what bug#'s correspond to the code checked into the nightly/milestone label so we can view the diffs as a transaction (individual diffs are available via SVN-update).