What needs to be done between 0.9 and 1.0?

[Stefan Arentz <st...@gmail.com>]

I'm interested to use OpenJPA in my current project instead of
Hibernate but the version number scares me. Can anyone explain maybe
in bit more detail what the status of OpenJPA is and what kind of
things are on the todo between now and 1.0?

 S.

Re: RE: What needs to be done between 0.9 and 1.0?

[Stefan Arentz <st...@gmail.com>]

On 8/4/06, Patrick Linskey <pl...@bea.com> wrote:

...

> That said, we don't currently build jars or package up a proper release,
> and we don't currently have convenience shell scripts wrapping the
> handful of command-line tools that OpenJPA users will often execute. As
> you pointed out in your other thread, we haven't ported any bugs from
> our old bugzilla, and we haven't gotten a project plan in place yet.
> Expect to see movement on all of these issues over the coming weeks.
>
> I hope this helps answer your questions,

Hi Patrick,

Thank you for the detailed answer. It all sounds very reasonable.
Personally I will simpy use the time to learn the product and give
feedback.

The way you are building a commercial product on top of OpenJPA is
very interesting. Does that mean that there are a lot of extension
points in the OpenJPA code? Will these be documented?

For example, I am interested in building an extension that does more
advanced query logging together with Postgres' EXPLAIN ANALYZE kind of
query statistics. Is it going to possible to take OpenJPA and add
something like that to it?

 S.

RE: What needs to be done between 0.9 and 1.0?

[Patrick Linskey <pl...@bea.com>]

Hi,

Depending on your fear threshold, you shouldn't be scared off by the
version number.

OpenJPA is brand-new to Apache, so is in incubation. In the case of
OpenJPA, this means that we're working on building a community around
OpenJPA, and are learning to operate as a team in a way that meshes with
the distributed, multi-organizational ways of successful Apache
projects. Essentially, incubation for us is a time to learn how to be
good Apache citizens.

However, OpenJPA is not a new codebase. The Kodo codebase dates back
several years, and OpenJPA is a direct subset of that codebase. At BEA,
we're building the next version of Kodo (4.1) on top of OpenJPA. That
is, Kodo doesn't use a forked codebase or any replacement classes or
anything like that; it's pure OpenJPA with a number of plug-ins and
extensions.

So, you should find that OpenJPA is quite stable as a product. The 0.9
version number reflects the newness of the OpenJPA project at Apache,
not the newness of the code itself. It's my understanding that we won't
change the number to 1.0 until we get out of the incubator, although
that might be a misconception on my part.

That said, we don't currently build jars or package up a proper release,
and we don't currently have convenience shell scripts wrapping the
handful of command-line tools that OpenJPA users will often execute. As
you pointed out in your other thread, we haven't ported any bugs from
our old bugzilla, and we haven't gotten a project plan in place yet.
Expect to see movement on all of these issues over the coming weeks.

I hope this helps answer your questions,

-Patrick

-- 
Patrick Linskey
BEA Systems, Inc.  

> -----Original Message-----
> From: Stefan Arentz [mailto:stefan.arentz@gmail.com] 
> Sent: Friday, August 04, 2006 1:05 AM
> To: open-jpa-dev@incubator.apache.org
> Subject: What needs to be done between 0.9 and 1.0?
> 
> I'm interested to use OpenJPA in my current project instead 
> of Hibernate but the version number scares me. Can anyone 
> explain maybe in bit more detail what the status of OpenJPA 
> is and what kind of things are on the todo between now and 1.0?
> 
>  S.
> 
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.