Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of kwsutter@gmail.com designates
 209.85.218.214 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=QYij+lA5MQsLrdg4UpjkNLtyaU0WRpXlUoJpsDh90U1fM/FrcUNvvAgnkIp4nuCBpl
         J/lMN7jab+YMtCQ/snop01tERdipVYt86BjXIGausJC5RivnKVtNcdOpSD5fdjV5AZot
         B0aqM2NnPdlZvIuh1aD1YKiHl58MzFuz66k44=
MIME-Version: 1.0
In-Reply-To: <703e3136.5bdd4290.4b9ea6de.3439a@o2.pl>
References: <4B8FDFCB.9040404@apache.org> <4B969CC1.9070401@apache.org>
	 <703e3136.5bdd4290.4b9ea6de.3439a@o2.pl>
Date: Mon, 15 Mar 2010 16:58:33 -0500
Message-ID: <89c0c52c1003151458s10d15681peccbd91c27de061f@mail.gmail.com>
Subject: Re: Re: [DISCUSS] Upcoming OpenJPA 2.0.0 release plans
From: Kevin Sutter <kwsutter@gmail.com>
To: dev@openjpa.apache.org
Content-Type: multipart/alternative; boundary=00032555b95a7c74460481ddfb02

--00032555b95a7c74460481ddfb02
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Milosz,
I actually thought we were doing a pretty good job of updating the
documentation for the new JPA 2 level of functionality as we were
integrating the code changes.  Not sure what aspect of lock modes you are
referring to.  I can see where we have defined the new JPA 2 lock mode as
well as kept the old openjpa lock modes.

So, personally, I don't think we're too far off.  Of course, with enough
examples, I can be educated...  :-)  I know that we have your general doc
update JIRA.  But, maybe we need to open subtasks for the larger areas of
the documentation that still need some work.

Thoughts?
Kevin

On Mon, Mar 15, 2010 at 4:30 PM, Mi=C5=82osz <mtylenda@o2.pl> wrote:

> Hi All,
>
> What worries me is that our documentation is still a JPA 1 documentation =
in
> many places. For example we say only two lock modes are available,
> subqueries are possible only in WHERE clause, etc. That is confusing,
> especially for JPA new-comers and might turn into quite a big job. I am
> currently correcting the user manual in small steps but not able by any
> chance to fix all the scattered inaccuracies before 2.0 time.
>
> Regards,
> Milosz
>
> > As we approach the March 19 branch creation for 2.0.0, please take time
> > to review JIRA issues that either you have opened or are assigned to
> > where the Fix Version is 2.0.0 or 2.0.1 and start reassigning to:
> >
> > 2.0.1 - maintenance release, which will not be open to just any patch
> > 2.1.0 - next trunk release, which will be open to any patches
> > None - you have no intention of working on the issue in the foreseeable
> > future
> >
> >
> > Thanks,
> > Donald
> >
> >
> > On 3/4/10 11:28 AM, Donald Woods wrote:
> > > As we're winding down the changes for the 2.0.0 release, I wanted to
> > > alert everyone to the proposed release dates.
> > >
> > > 3/19 - Cut 2.0 branch
> > > 4/12 - Start release candidate vote
> > >
> > > Once the branch is created, only changes approved by myself or Kevin
> > > will be accepted into the branch.  Trunk (probably renamed to 2.1) wi=
ll
> > > still be open for any changes.
> > >
> > > Also, please use this email thread to discuss any critical patches th=
at
> > > you would like to see considered for 2.0.0.
> > >
> > >
> > > Thanks,
> > > Donald
> > >
>
>

--00032555b95a7c74460481ddfb02--