I just went through and updated the Fix Version based on when the subversion commits actually occurred (all went into Beta2) and updated the CHANGES.txt and RELEASENOTES.html accordingly.
-Donald On 3/7/10 11:51 AM, Michael Dick wrote: > Hi Milosz, > > Regarding the writebehind items I was using the fix for as a goal. The > issues are still open (reopened) and shouldn't be considered done though. > When the time comes to release 2.1 they'll have to be re-targeted or > completed. I can un-target them though. > > Looking at this > page<http://issues.apache.org/jira/secure/BrowseProject.jspa?id=12310351&subset=-1>shows > the the remaining issues for each release. Since we don't have a 2.1.0 > version, we should move the issues that you've found to 2.0.0 (I'll go ahead > and do that). > > Thanks for pointing it out. > > -mike > > On Sun, Mar 7, 2010 at 6:32 AM, Miłosz Tylenda <[email protected]> wrote: > >> Hello All, >> >> I noticed the following issues have Fix Version field set to 2.1.0 but the >> code has been committed into trunk. I suggest the Fix Version be changed to >> 2.0.0 or the code rolled back from trunk. >> >> OPENJPA-1483 count (Distinct e) in JPQL gives wrong result when the id >> field is a compound primary key >> OPENJPA-1486 Lazy fetched embeddable should not be materialized in the >> query result >> OPENJPA-1496 Fail to set temporal parameter >> OPENJPA-1517 Reduce locking in LifecycleEventManager >> >> There are also a few 2.1.0 items related to writebehind cache but from what >> I can see these were rolled back. >> >> Regards, >> Milosz >> >> >
