Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Development"
(→Project Status/News) |
|||
Line 52: | Line 52: | ||
== Project Status/News == | == 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. | * 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]] | * Feb 8, 2009 - [[EclipseLink/Maven | Maven repository available]] | ||
* Nov 12, 2007 - [http://www.eclipse.org/eclipselink/downloads/ Nightly development builds, available for download.] | * 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. | * Aug 27, 2007 - All IPZilla bugs approved. Initial source contribution checked-in. | ||
− | |||
− | |||
</td> | </td> |
Revision as of 14:32, 14 July 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 not required for bug fixes. Prior to code being checked in, code reviews will be done through the mailing list (eclipselink-dev@eclipse.org). |