Thanks for the comments, but I don't think any of the below requires a new release candidate, given this is a Beta release :-)
For #1 - I just followed what we had done for the Milestone releases, in that only items mentioned in Iterations 12 - 14 made it onto this list. For the final release, we'll want to create an overview section that covers all the iterations and "talks up" the release. For #2 - The openjpa-osgi module has been in the source code since before M3, but is not being built. Before the final release, I would expect either we import the code from Apache Aries to finish this module or remove it until a future release. For #3 - There was nothing mentioned in I12-I14 about performance, so nothing was added. Also, that was one of the reasons of releasing this as a Beta, so we could continue to work on performance improvements, which can be collected into one section in the final release notes. For #4 - The link works for me from home using Firefox. Try it again, as is typical with the Apache servers, sometimes they are under heavy load and just need some time before retrying.... -Donald On 1/26/10 10:55 AM, Pinaki Poddar wrote: > > Hi, > Looks pretty good. Few comments before I vote :) > > 1. The release notes Overview section says > > * Passes the Sun JPA 2.0 TCK > * Implements the final JSR-317 JPA 2.0 specification APIs > * Supports the final JSR-303 Bean Validation 1.0 specification APIs > * Extended lock scope support > * Support for CacheRetrieve/StoreMode properties on find/refresh methods > * Updated find/refresh methods to support entity manager level > properties > * Reworked support for delimited identifiers > > The wide variation in granularity/import of these bullet items reads > strange. As if passing JPA 2.0 TCK and "Updated find/refresh" are somewhat > at the sevel of import :) > > This paragraph being the first section of the release notes should be > reworked to describe only the significant aspect of the release. > > 2. openjpa-osgi > A module has appeared which has not been mentioned either in the > documentation or in the release notes. The single Java source code for it > shows comments that should be removed. Actually, to include as openjpa-osgi > as module at all within the distribution will require at least some > documentation. > > 3. May be we should add few words in Overview section about the outcome of > the performance improvement activities. > > 4. http://people.apache.org/~dwoods/openjpa/2.0.0-beta/staging-site/ > The links from this page are 404 > > > > > > > > > > > > > ----- > Pinaki
