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"

(EclipseLink Development Process)
(Links)
 
(142 intermediate revisions by 14 users not shown)
Line 1: Line 1:
=== Eclipe Persistence Services Development ===
+
__NOTOC__
This is the landing page for all things development. 
+
<table border="0"  width="100%" cellspacing="6">
 +
<tr>
  
=== EclipseLink Development Process ===
+
<td valign="top">
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 prioitized [[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 componant.
+
<table>
  
== Features and Enhancements ==
+
<tr>
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).
+
<td valign="top">
 +
<table width="100%" cellpadding="0" cellspacing="0">
 +
<tr>
 +
<td valign="top" style="background-color: #cff8d9; border-width: 1px; border-style: solid; border-color: #999999; padding: 10px;">
 +
== Current Development ==
 +
* Development has moved from SVN to Git, see [[EclipseLink/Development/Process/Git|Git]]
  
== Bugs ==
+
* [[EclipseLink/Development/2.7.0]]
Docs are usually note required for bug fixes.  Prior to code being checked in, code reviews will be done through the mailing list (eclipselink-dev@eclipse.org).
+
** Development being done in '''/git/master/'''
  
== Design Docs ==
+
* [[EclipseLink/Development/2.6.0]]
[[EclipseLink/Development/DesignDocs/Template|design doc template]]
+
** Maintenance releases from 2.6 branch
 +
 
 +
* [[EclipseLink/Development/2.5.0]]
 +
** Maintenance releases from 2.5 branch
 +
</td>
 +
</tr>
 +
<tr>
 +
<td valign="top">
 +
 
 +
== Features, Bugs & Enhancements ==
 +
Features and Enhancements will have a BugZilla [[EclipseLink/Development/Bugs|enhancement]] associated with it.  A [[EclipseLink/Development/DesignDocs|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 [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).
 +
 
 +
== EclipseLink Newsgroups & Mailing Lists ==
 +
* [http://www.eclipse.org/forums/index.php?t=thread&frm_id=111 EclipseLink Users Forum]
 +
* [http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/maillist.html EclipseLink Dev Mailing list - eclipse.org hosted - date view] - [http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/ month view] - [https://dev.eclipse.org/mailman/listinfo/eclipselink-dev subscribe]
 +
* [http://dev.eclipse.org/mhonarc/lists/eclipselink-users/maillist.html EclipseLink Users Mailing list - eclipse.org hosted - date view] - [http://dev.eclipse.org/mhonarc/lists/eclipselink-users/ month view] - [https://dev.eclipse.org/mailman/listinfo/eclipselink-users subscribe]
 +
* [http://eclipse.1072660.n5.nabble.com/EclipseLink-f4.html EclipseLink Nabble Forums] - [http://eclipse.1072660.n5.nabble.com/EclipseLink-Users-f5.html users] - [http://eclipse.1072660.n5.nabble.com/EclipseLink-Dev-f7490.html dev]
 +
</td>
 +
</tr>
 +
 
 +
</table>
 +
</td>
 +
 
 +
<td rowspan="3" width="310" valign="top">
 +
<table>
 +
<tr><td style="background-color: #bbbad2; border-width: 1px; border-style: solid; border-color: #fabd23; padding: 10px;">
 +
 
 +
=== Links ===
 +
* [http://www.eclipse.org/eclipselink EclipseLink Home]
 +
 
 +
* [[EclipseLink/Development/DesignDocs|Design documents]]
 +
 
 +
* [[EclipseLink/Development/Process/Git|Git]] - source code repository
 +
 
 +
* [[/Process|Contribution/Development Process]] - overview of development process
 +
* [[EclipseLink/Building| Building & Testing]] - how to build and test EclipseLink
 +
* [[/Testing|Testing]] - more information on EclipseLink testing
 +
 
 +
* [[EclipseLink/Maven|Maven]] - EclipseLink in Maven
 +
 
 +
* [http://www.eclipse.org/eclipselink/#download Downloads]
 +
 
 +
* [[EclipseLink/Development/Incubator|Incubator]] - where experimental ideas are developed
 +
* [[EclipseLink/IPLog | IP Log, Dependencies]] - where all external contributions and dependencies must be tracked
 +
 
 +
* [[EclipseLink/Development/Bugs|Bugs and Enhancements]]
 +
 
 +
====Resources, Documentation====
 +
* [https://www.openhub.net/p/eclipselink Open HUB] - open source project network
 +
 
 +
* [[EclipseLink/Development/Architecture/EclipseLink|EclipseLink Architecture]]
 +
* [[EclipseLink/Development/Summit|EclipseLink Summit 2010]]
 +
 
 +
</td></tr></table>
 +
</td>
 +
</tr>
 +
</table>
 +
 
 +
[[Category:EclipseLink|Development]]

Latest revision as of 14:04, 18 April 2015

Current Development

  • Development has moved from SVN to Git, see Git

Features, Bugs & Enhancements

Features and Enhancements will have a BugZilla enhancement associated with it. A 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

Links

  • Git - source code repository
  • Maven - EclipseLink in Maven

Resources, Documentation

Back to the top