EclipseLink/Development

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.

http://fisheye2.atlassian.com/chart/~charttype=Area,date1=2008-01-01,stacktype=None/eclipselink/?authorHistoryChart=authorMap&w=400&h=200 Links EclipseLink Home Downloads FishEye Testing Performance IP Log Building EclipseLink Developer Meetings minutes and agendas Information about EclipseLink Maven Repository Category:EclipseLink Category:EclipseLink:Users Category:EclipseLink:Committers Newsgroups & Mailing Lists EclipseLink Newsgroup EclipseLink Nabble Forums EclipseLink Developers Mailing List EclipseLink Users Mailing List Blogs EclipseLink Team Blog Doug's Java Persistence Blog Development Documents Wiki Organization Dependencies Design documents Architecture documents End-user documentation plan

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 - 1.0M8 development milestone VIII completed, and available for download. May 9, 2008 - 1.0M7 development milestone VII completed, and available for download. Feb 8, 2009 - Maven repository available Nov 12, 2007 - Nightly development builds, available for download. Nov 5, 2007 - 1.0M1 initial development milestone I completed, and available for download. Aug 27, 2007 - All IPZilla bugs approved. Initial source contribution checked-in. Project Timeline Project Road Map 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).