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"

(Links)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
 
<table border="0"  width="100%" cellspacing="6">  
 
<table border="0"  width="100%" cellspacing="6">  
 +
<tr>
 +
<td valign="top">
 +
 +
<table>
 
<tr>
 
<tr>
 
<td>
 
<td>
Line 8: Line 12:
  
 
</td>
 
</td>
 +
</tr>
 +
<tr>
 +
<td>
 +
<table width="100%" height="100%" cellpadding="0" cellspacing="0">
 +
<tr>
 +
<td style="background-color: #cff8d9; border-width: 1px; border-style: solid; border-color: #999999; padding: 10px;">
 +
 +
== Project Status/News ==
 +
 +
* July 10, 2008 - 1.0.1 branch created for 1.0 patches, trunk open for new 1.1 development.
 +
* July 9, 2008 - [http://www.eclipse.org/eclipselink/downloads/ EclipseLink 1.0 Released!]
 +
* June 12, 2008 - Moving the EclipseLink project from Technology to RT. this will effect SVN, build, test, newsgroup, download locations.
 +
* Feb 8, 2009 - [[EclipseLink/Maven | Maven repository available]]
 +
* Nov 12, 2007 - [http://www.eclipse.org/eclipselink/downloads/ Nightly development builds, available for download.]
 +
* Aug 27, 2007 - All IPZilla bugs approved. Initial source contribution checked-in.
 +
 +
</td>
 +
</tr>
 +
</table>
 +
</td>
 +
</tr>
 +
 +
<tr>
 +
<td>
 +
=== EclipseLink Development Process ===
 +
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.  The [[EclipseLink/Development/SprintList|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 [[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 bug fixes.  Prior to code being checked in, code reviews will be done through the mailing list (eclipselink-dev@eclipse.org).
 +
 +
</td>
 +
</tr>
 +
 +
</table>
 +
</td>
 +
 
<td rowspan="2" width="310" style="background-color: #bbbad2; border-width: 1px; border-style: solid; border-color: #fabd23; padding: 10px;">
 
<td rowspan="2" width="310" style="background-color: #bbbad2; border-width: 1px; border-style: solid; border-color: #fabd23; padding: 10px;">
  
Line 42: Line 85:
 
* [[EclipseLink/Development/Architecture|Architecture documents]]
 
* [[EclipseLink/Development/Architecture|Architecture documents]]
 
* [[EclipseLink/Development/Documentation|End-user documentation plan]]
 
* [[EclipseLink/Development/Documentation|End-user documentation plan]]
 
</td>
 
</tr>
 
<tr valign="bottom">
 
 
<td>
 
<table width="100%" height="100%" cellpadding="0" cellspacing="0">
 
<tr>
 
<td style="background-color: #cff8d9; border-width: 1px; border-style: solid; border-color: #999999; padding: 10px;">
 
 
== Project Status/News ==
 
 
* July 10, 2008 - 1.0.1 branch created for 1.0 patches, trunk open for new 1.1 development.
 
* July 9, 2008 - [http://www.eclipse.org/eclipselink/downloads/ EclipseLink 1.0 Released!]
 
* June 12, 2008 - Moving the EclipseLink project from Technology to RT. this will effect SVN, build, test, newsgroup, download locations.
 
* Feb 8, 2009 - [[EclipseLink/Maven | Maven repository available]]
 
* Nov 12, 2007 - [http://www.eclipse.org/eclipselink/downloads/ Nightly development builds, available for download.]
 
* Aug 27, 2007 - All IPZilla bugs approved. Initial source contribution checked-in.
 
 
</td>
 
</tr>
 
</table>
 
 
=== EclipseLink Development Process ===
 
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.  The [[EclipseLink/Development/SprintList|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 [[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 bug fixes.  Prior to code being checked in, code reviews will be done through the mailing list (eclipselink-dev@eclipse.org).
 
  
 
</td>
 
</td>

Revision as of 14:41, 14 July 2008

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.

Project Status/News

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

Links

Newsgroups & Mailing Lists

Blogs

Development Documents

Back to the top