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.
Difference between revisions of "EclipseLink/Development"
(→Links) |
(→Project Status/News) |
||
| Line 51: | Line 51: | ||
== Project Status/News == | == Project Status/News == | ||
| + | |||
| + | * June 12, 2008 - Moving the EclipseLink project from Technology to RT. this will effect SVN, build, test, newsgroup, download locations | ||
* June 5, 2008 - [http://www.eclipse.org/eclipselink/downloads/ 1.0M8 development milestone VIII completed, and available for download.] | * June 5, 2008 - [http://www.eclipse.org/eclipselink/downloads/ 1.0M8 development milestone VIII completed, and available for download.] | ||
* May 9, 2008 - [http://www.eclipse.org/eclipselink/downloads/ 1.0M7 development milestone VII completed, and available for download.] | * May 9, 2008 - [http://www.eclipse.org/eclipselink/downloads/ 1.0M7 development milestone VII completed, and available for download.] | ||
Revision as of 12:44, 13 June 2008
Welcome to the Eclipse Persistence Services Project (EclipseLink) Development HomeThis page is focussed on information about current development and development process for the comitters of the EclipseLink project. |
Links
Newsgroups & Mailing Lists
BlogsDevelopment Documents |
EclipseLink Development ProcessThe 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 EnhancementsFeatures 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). BugsDocs 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). |