openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin" <robertburrelldon...@gmail.com>
Subject Re: JPA 2.0 Development Kickoff
Date Tue, 25 Nov 2008 22:02:19 GMT
On Tue, Nov 25, 2008 at 5:54 PM, Kevin Sutter <kwsutter@gmail.com> wrote:
> Hi,
> With the recent posting of Public Review Draft of the JPA 2.0 specification
> [1], we need to publicly kick off the development of JPA 2.0 within the
> OpenJPA development team.  There have been a few other related postings to
> the dev mailing list [2].  This shows the team's interest in pursuing this
> goal of delivering JPA 2.0.  To that end, we're going to borrow a few ideas
> from our brethern over at the OpenEJB project [3] and other Agile-like
> practices.

sounds interesting :-)

> One of these ideas is to outline short iterations (or sprints) that will
> constitute various pieces of runnable function.  For example, our first
> iteration has to include the JPA 2.0 API (JIRA issue OPENJPA-773).  With
> this code drop, developers will be able to compile and build with the new
> enhanced API.  Not all of the function will be implemented in the first
> iteration, but hopefully a customer application written against the JPA 2.0
> spec should be buildable.  I'm sure the first iteration will have additional
> functionality, but the JPA 2.0 API is an example of what to expect.
>
> Every iteration will need to be self-contained.  Not only will a given
> function need be implemented, but it also needs corresponding test cases and
> documentation.  This doesn't mean that a given feature of JPA 2.0 has to be
> 100% complete in a single iteration.  For example, the Criteria API would be
> difficult to contain within a single iteration.  But, the Criteria API could
> be broken down into smaller bite-size pieces and spread across 2 or more
> iterations.  Each of these bite-size pieces still need to be complete from a
> functional, test, and documentation perspective.

cool

> To that end, we will need several different types of participation:
>
> Developers:  People interested in accepting responsibility for developing
> (design, implementation, and unit test) any particular function.
> ID:  People interested in helping out with the documentation of a particular
> function.
> Testers:  People interested in actively testing, especially from a customer
> viewpoint.
>
> In many cases, the same people will be involved in all three aspects.  But,
> depending on time commitments, some people will only be able to sign up for
> one aspect.  For example, I would guess (hope) that we have several people
> interested in testing out the new function available in JPA 2.0.  As each
> iteration is defined and the JIRA issues are opened up, it would be great to
> have these people indicate a desire to help test the various functions
> defined.  Since the actual design and implementation of a new function may
> require more dedicated time, the pool of people to select from may be
> smaller.  We will welcome all interested in participating!
>
> Another area that OpenJPA needs some help is with Samples.  As we start on
> our JPA 2.0 implementation, I would really like to grow our Samples base.
> Starting off extremely simple and growing to more complex would be ideal.
> If any of you have ideas on how to organize and expand on our Samples, they
> would be appreciated.

perhaps it might be possible to base some samples on usage in other
open source projects

- robert

Mime
View raw message